Skip to content

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

Closed

Conversation

bergmeister
Copy link
Contributor

@bergmeister bergmeister commented Oct 3, 2019

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)

@bergmeister bergmeister changed the title legacy/1.x: Backport #909 and update .Net SDK version to be the same as in master 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) Oct 3, 2019
@@ -34,7 +34,7 @@ if ($PSVersionTable.PSEdition -ne "Core") {

task SetupDotNet -Before Clean, Build, TestHost, TestServer, TestProtocol, TestPowerShellApi {

$requiredSdkVersion = "2.0.0"
Copy link
Contributor Author

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

@bergmeister
Copy link
Contributor Author

bergmeister commented Oct 3, 2019

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

@bergmeister
Copy link
Contributor Author

@PoshChan please retry

@PoshChan
Copy link

PoshChan commented Oct 3, 2019

@bergmeister, I do not understand: please retry

Commands available in this repo for you:
  • get failures this will attempt to get the latest failures for all of the target pipelines
  • remind me in <value> <units> this will create a reminder that will be posted after the specified duration <value> is a number, and <units> can be minutes, hours, or days (singular or plural)

@TylerLeonhardt
Copy link
Member

@bergmeister I usually just use the checks tab

@TylerLeonhardt
Copy link
Member

The legacy branch is an odd one. It targets net451 and netstandard1.3 I believe. It might not be worth making this change.

@TylerLeonhardt
Copy link
Member

#1103 has a lot of this code change in it. Closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants