-
Notifications
You must be signed in to change notification settings - Fork 178
Added support for net7.0 #682
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
Conversation
filipw
left a comment
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.
thanks! let' get rid of 5.0 too
|
@filipw Removed I don't seem to have the permissions to change the settings 😃 |
|
done, thanks!! |
|
Great. I'll release this then?. After that Omnisharp needs to be updated with the latest dotnet-script packages. 👍🙂 |
This PR adds support for the upcoming
net7.0which is currently in RC1.Removed support for
netcoreapp3.1netcoreapp3.1reaches EoS (End of Support) on December 13, 2022 and we now supportnet5.0,net6.0andnet7.0.Moved build to Github Actions
The build has been moved from Azure Devops to GitHub Actions. The old build was sort of a mess and a lot was cleaned up here. All jobs now basically have the exact same setup.
OmniSharp
Dotnet.Script.DependencyModelandDotnet.Script.DependencyModel.Nugetneed to be updated in Omnisharp to supportnet7.0. We used to have a framework check inCompilationDependencyResolverwhich was a leftover from when we supportednetcoreapp2.1. This check is now removed meaning that with regards tonetcoreapp3.1which still has a couple of months left, it will still work for resolving compilation dependencies.Versions
The versions has been bumped to 1.4.0 leaving a bit of room if we should need to fix something before
netcoreapp3.1goes out of support.In my opinion we can release this now and get
Dotnet.Script.DependencyModelandDotnet.Script.DependencyModel.Nugetupdated in Omnisharp in good time beforenet7.0goes RTM.Hopefully a new version of OmniSharp will be released by then and we avoid resolving to
latestfor users that wants to start usingnet7.0Build Script
Just a couple of path-related issues where we in the past assumed running the script from the
buildfolder.