FSharp.Core version warning (net7.0)
See original GitHub issueDescribe the bug
Following what I suspect to be this change, I now get the following warning after upgrading to version 3.3.0:
[NU1608] Detected package version outside of dependency constraint: FsToolkit.ErrorHandling 3.3.0 requires FSharp.Core (= 4.7.2) but version FSharp.Core 7.0.0 was resolved.
To Reproduce Steps to reproduce the behavior:
- Add
FsToolkit.ErrorHandling.TaskResultversion3.3.0to anet7.0project. - Build the project.
Expected behavior No warning.
Desktop:
- OS: macOS 13.0
Issue Analytics
- State:
- Created 10 months ago
- Comments:14 (3 by maintainers)
Top Results From Across the Web
Announcing F# 7 - .NET Blog
Because of the potential drawbacks, we will emit a warning when interfaces with static abstract methods are declared and implemented in F#. ...
Read more >FSharp.Core 7.0.400
FSharp.Core redistributables from F# Tools version 12.7.0 For F# 7.0. Contains code from the F# Software Foundation.
Read more >In Visual Studio 2022, why are my F# projects looking for " ...
I recently upgraded to Visual Studio 2022, Version 17.1.0 Preview 1.0. Now when I build, I get errors about FSharp.Core, as pictured below....
Read more >No support for FSharp.Core 4.7 - Developer Community
This issue is read only, because it has been in the Closed - Fixed state for over 90 days. It was closed for...
Read more >Release Notes
All fake modules are now compiled for netstandard2.0 , net462 and FSharp.Core 4.7 , you should consider to upgrade your runtime. ENHANCEMENT: Fake.DotNet....
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 Free
Top 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

I already pulled the official version. Please refer the paket issue I filled as that’s the root cause.
Ah paket has changed rules around its version. Lemme see if I can clean it up