Skip to content
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

Closed
tintoy opened this issue Nov 10, 2020 · 8 comments
Closed

Upgrade to .NET Core 3.1 #20

tintoy opened this issue Nov 10, 2020 · 8 comments

Comments

@tintoy
Copy link
Owner

tintoy commented Nov 10, 2020

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

@amshtemp
Copy link

amshtemp commented Nov 12, 2020

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

@tintoy
Copy link
Owner Author

tintoy commented Nov 12, 2020

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.

@tintoy
Copy link
Owner Author

tintoy commented Nov 29, 2020

For now, I'm going to target netcoreapp3.1 rather than net5 since the 3.1 runtime is a much smaller download than the 3.1 SDK.

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 😉

@tintoy
Copy link
Owner Author

tintoy commented Nov 29, 2020

Ok - will publish the VSIX package after I've had more time to do testing. If anyone else needs it sooner, here it is:

msbuild-project-tools-0.3.11.zip

@tintoy
Copy link
Owner Author

tintoy commented Nov 29, 2020

(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)

@aneeskodappana
Copy link

@tintoy any updates on 5.0.* support

@tintoy
Copy link
Owner Author

tintoy commented Jan 17, 2021

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 :)

@tintoy
Copy link
Owner Author

tintoy commented Jan 17, 2021

(but longer term I hope we can look at moving over sometime in February or March)

tintoy added a commit that referenced this issue Jan 29, 2021
… installed

#20

Also, remove legacy ("classic") completion provider.
tintoy added a commit to tintoy/msbuild-project-tools-vscode that referenced this issue Jan 29, 2021
@tintoy tintoy closed this as completed Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants