FsCheck installing FSharp.Core
See original GitHub issueThis package, or the current version of it available from Nuget, is installing FSharp.Core v3.1.2.5. This process overwrites the provided VS version, in my case v4.4.0.0 of VS2015 Community Edition. The consequence is version conflicts causing execution failure at runtime. Fortunately, this occurred during unit tests.
The problem is resolved by replacing the referenced FSharp.Core with the VS provided version at:
%ProgramFiles(x86)%\Reference Assemblies\Microsoft\FSharp\.NETFramework\v4.0\4.4.0.0\FSharp.Core.dll
Issue Analytics
- State:
- Created 8 years ago
- Comments:20 (14 by maintainers)
Top Results From Across the Web
FSharp.Core 7.0.400
FsCheck. FsCheck is a tool for testing .NET programs automatically. You provide a specification of the program, in the form of properties which...
Read more >FsCheck 2.16.6
FsCheck helps you to define properties, observe the distribution of test data, and define test data generators. Crucially, when a property fails, FsCheck...
Read more >Install F# | Microsoft Learn
Install F# with Visual Studio Code ... Select the Extensions icon and search for "Ionide": The only plugin required for F# support in...
Read more >Announcing F# 7 - .NET Blog
We're happy to announce the availability of F# 7, shipping with .NET 7 and Visual Studio 2022. Check out this next step to...
Read more >Quick Start
First install FsCheck, open an fsx file and start with: ... Core.dll, open namespace FsCheck, change the language to "C# statements" and you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you @kurtschelfthout, binding redirect makes the trick
Make sure all versions of FSharp.Core in your solution are the same, and make sure the test assembly has an app.config with binding redirects for FSharp.Core to the latest version.