I'm also having this issue. Any fix?

I don't know. Project was discontinued.
It was used in IE extension , officially they not support managed code .

I'm seeing this issue when I try to open FSharp.Data.HttpRequestHeaders and reference it in code. My entire project breaks until I remove references to that specific library. Any thoughts on this?

Sorry,
can't help you.
The issue was not resolved.

@fischgeek this is probably a binding redirects issue, you may have several F# libraries / projects depending on different versions of FSharp.Core.

https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/redirect-assembly-versions

The general fix is to adjust app.config with a binding redirect declaration unifying the version of FSharp.Core (or any library that clashes) to the one that your application ships.

@smoothdeveloper - Thanks for the reply. I still think FSharp.Data is using an old version of .Core. I spent a lot of time trying to isolate the issue.

So, I unloaded all attached F# projects and built the main project (web project). I referenced only 1 F# library project (just a few helper methods). One helper method is using FSharp.Data.HttpRequestHeaders.

With the library as-is running on the latest .Core version, the build succeeds but the site throws the code dump screen.

When I comment out the 1 line that references FSharp.Data.HttpRequestHeaders the site works.

Interesting, right?

EDIT: Here is my binding redirect in the F# lib.

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="FSharp.Core" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-999.999.999.999" newVersion="4.7.1.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

@cartermp We should go through and clean out old issues for this repo.

@dsyme sounds gouda me, wanna find time for a zoom or teams call to just collab on it sometime this week or next?