-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mismatch FSharp.Core.dll WebSharper31.exe.config and msbuild #523
Comments
You can see in more detail from the binding log what's going, that despite the error message being a lack of finding 4.3.0.0 it's the substituted 4.3.1.0 bind:
|
We've also been seeing an equivalent issue when attempting a "Clean" under Visual Studio on projects that contain WebSharper -
I'm able to workaround this issue by altering the project from: |
Mainly for my own reference, to get F# 3.1 / 4.3.1.0 support, the steps you need are, edit (need administrator rights):
to include: <dependentAssembly>
<assemblyIdentity name="FSharp.Core" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.3.1.0" newVersion="4.3.1.0" />
</dependentAssembly> Then register the dll with gacutil (you may have to find an installer this):
|
Closing as outdated 3.x issue. |
Related to issue #504
There's a mismatch between the included version of FSharp.Core.dll (4.3.0.0) and what's configured in msbuild WebSharper31.exe.config which has:
When you run under msbuild e.g. automated builds you'll get failures like:
packages\WebSharper.3.6.7.227\build\WebSharper.targets (60, 5)
The "WebSharperTask" task failed unexpectedly.
System.IO.FileNotFoundException: Could not load file or assembly 'FSharp.Core, Version=4.3.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'FSharp.Core, Version=4.3.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
You could separate out WebSharper31.exe and WebSharper40.exe and ship a separate FSharp.Core.dll. As workaround I've substituted in the 4.3.1.0 dlls which works for me as a temporary fix.
The text was updated successfully, but these errors were encountered: