-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Update packages and frameworks #488
Update packages and frameworks #488
Conversation
b5f1d8b
to
a2d4d94
Compare
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
a2d4d94
to
a938051
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
b93c75f
to
9734ebd
Compare
This comment was marked as outdated.
This comment was marked as outdated.
<PackageReference Update="FSharp.Core" Version="[4.6.2, 99]" /> | ||
<PackageReference Update="FSharp.Core" Version="[6.0.5, 99]" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we have to make this change? It is causing a problem described in #509.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We were using some of the newer features in some of the code, but I'm sure there are workarounds. I don't remember specifics though.
Update to .NET 6.0 (LTS) and .NET Framework 4.8 as per Microsoft recommendations. .NET Framework 4.6.1 is out of support and .NET 5.0 is not LTS.
Also updated all packages to latest and consolidated versions.