You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you do a paket update today on the latest template, it'll move fsharp.core to v6 despite the project being .net 5. we should pin it to 5 using ~> 5.
Also we should add a refs file to Shared with FSharp.Core in it (and maybe to the build refs as well?).
The text was updated successfully, but these errors were encountered:
Tomasz and I agreed about pinning for Client/Server. We're not certain whether it's necessary to do anything with Shared as it may use whatever Client/Server do.
If you do a paket update today on the latest template, it'll move fsharp.core to v6 despite the project being .net 5. we should pin it to 5 using
~> 5
.Also we should add a refs file to Shared with FSharp.Core in it (and maybe to the build refs as well?).
The text was updated successfully, but these errors were encountered: