-
Notifications
You must be signed in to change notification settings - Fork 234
legacy/1.x: Backport #909 to use global.json to pin .Net Core SDK version and update .Net SDK version to be the same as in master (2.1.801) #1054
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
@@ -34,7 +34,7 @@ if ($PSVersionTable.PSEdition -ne "Core") { | |||
|
|||
task SetupDotNet -Before Clean, Build, TestHost, TestServer, TestProtocol, TestPowerShellApi { | |||
|
|||
$requiredSdkVersion = "2.0.0" |
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.
Note that 2.0 has already reached the end of its life a year ago!
https://dotnet.microsoft.com/download/dotnet-core
It seems changing the SDK from 2.0 to 2.1 breaks the Windows builds in different ways. One of them is that dotnet xunit has been deprecated |
@PoshChan please retry |
@bergmeister, I do not understand: please retry Commands available in this repo for you:
|
@bergmeister I usually just use the checks tab |
The legacy branch is an odd one. It targets net451 and netstandard1.3 I believe. It might not be worth making this change. |
74320f7
to
809d244
Compare
#1103 has a lot of this code change in it. Closing this. |
Backport #909 to use global.json to pin .Net Core SDK version and update .Net SDK version to be the same as in master.
This makes the 2 branches not only more consistent but makes building locally easier (I could not build the legacy branch at first yesterday because I have the .Net Core 3 SDK installed)