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

Move to a 2.1.300-preview build of .NET Core SDK #24591

Closed
nguerrera opened this issue Feb 2, 2018 · 2 comments
Closed

Move to a 2.1.300-preview build of .NET Core SDK #24591

nguerrera opened this issue Feb 2, 2018 · 2 comments
Assignees
Milestone

Comments

@nguerrera
Copy link
Contributor

nguerrera commented Feb 2, 2018

Currently the roslyn build depends on a daily build of .NET Core SDK 2.2.0-preview. However, following dotnet/designs#29, the .NET Core SDK release that was going to be named 2.2 is now named 2.1.300. So recent 2.1.300 builds are actually newer than historical 2.2.0 builds.

Roslyn moving to a 2.1.300 build helps in several ways:

  1. We shouldn't reference 2.2.0 SDK in the contributor docs since it no longer corresponds to a real upcoming version of the SDK.
  2. Installing a 2.2.0 build on your machine will shadow 2.1.300 so you'll be using this build instead of a 2.1.300 preview (that is really newer) in projects without global.json (*)
  3. We'd like to get roslyn on to a newer build to get more dogfooding coverage of recent SDK changes (particularly around build perf).

(*) Folks should also be instructed somewhere to uninstall any 2.2.0-preview on their machines when installing 2.1.300-preview.

cc @jaredpar

@nguerrera
Copy link
Contributor Author

Folks should also be instructed somewhere to uninstall any 2.2.0-preview on their machines when installing 2.1.300-preview.

Link to dotnet/announcements#57

@jaredpar
Copy link
Member

done.

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

2 participants