-
Notifications
You must be signed in to change notification settings - Fork 16
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
Upgrade to .NET Core 3.1 #20
Comments
MS is abandoning the old mantra of "let's do little upgrade" and more pushing towards more progressive and rapid updates. IMHO I think msbuild-project-tools-server should follow suit and upgrade to 5.0 too. Edit: You can also install 3.0 SDK and 5.0 runtime |
Yeah as long as the 5.0 runtime can be installed without affecting people stuck on 3.1 that could be ok but I’ll need to do some research to see how that affects system requirements etc. |
For now, I'm going to target If we hit any blockers, I'll revisit this but for now it should do a good enough job of spreading the pain out across all of our users 😉 |
Ok - will publish the VSIX package after I've had more time to do testing. If anyone else needs it sooner, here it is: |
(that was pretty painful BTW, I may still consider upgrading to 5.0 if only because there were so many package version conflicts going from 3.0 to 3.1) |
@tintoy any updates on |
Hi - not planning to move over yet; want to see how the current version performs for a while before making another version jump for the runtime :) |
(but longer term I hope we can look at moving over sometime in February or March) |
… installed #20 Also, remove legacy ("classic") completion provider.
… installed tintoy/msbuild-project-tools-server#20 Also, remove legacy ("classic") completion provider.
3.1 is the LTS release and should be good until December 2022.
See official support policy:
https://dotnet.microsoft.com/platform/support/policy/dotnet-core
The text was updated successfully, but these errors were encountered: