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

.NET Core 2.1.1 released to nuget but no SDK/Runtime so error on run in VS.net #3241

Closed
JohnGalt1717 opened this issue Jun 19, 2018 · 15 comments

Comments

@JohnGalt1717
Copy link

Where is the SDK for .NET Core 2.1.1? You guys shouldn't be releasing packages to nuget until updates are ready on dot.net.

@RichardD2
Copy link

Exactly the same problem here. Why are the 2.1.1 packages even being offered to a site that's targeting 2.1.0 if they're just going to break it?

At least the new project file format makes it easier to downgrade, since you can't even do that from the package manager within Visual Studio.

@garethrampton
Copy link

This is a ridiculous situation. Surely the prerequisite SDK should be release prior to pushing the packages to nuget?

We faced the same issue with the official release of 2.1 where the full SDK release was a day or so behind.

@emasyakin
Copy link

emasyakin commented Jun 20, 2018

Following steps allowed me to get going on Win x64 platform:

@garethrampton
Copy link

@emasyakin-softheme Thanks.

I ended up using the version from here https://github.com/dotnet/versions/tree/master/build-info/dotnet/product/cli/release/2.1 which appears to be the RTM version anyway.

No need to uninstall previous SDK versions.

Just wish the ASP.NET Core team would get their act together with this kind of stuff.... and don't even get me started on the messed up versioning thats floating around the entire ecosystem.

@JohnGalt1717
Copy link
Author

That's still the preview release. If you install it you'll have to do the purge.

@garethrampton
Copy link

garethrampton commented Jun 20, 2018

Pretty sure that isn't the preview. The version certainly doesn't indicate it is: 2.1.301. I'm up and running with no purge required.

EDIT:
Both SDK links point to the exact same point: https://dotnetfeed.blob.core.windows.net/orchestrated-release-2-1/20180605-09/final/assets/Sdk/2.1.301-preview-008906/dotnet-sdk-2.1.301-win-x64.exe

@JohnGalt1717
Copy link
Author

Look at the file name you posted and tell me if it's the preview.... You WILL need a purge when the real final version is released.

@garethrampton
Copy link

Assuming nothing changes, then that build will indeed be the final build. (see notes here: https://github.com/aspnet/Home/wiki/.NET-Core-2.1.1-Early-Access-Downloads)

The final SDK version does appear to be available to download - just not published on the front-facing websites. For example, VSTS will happily download and use the full SDK if asked from here: https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.301/dotnet-sdk-2.1.301-win-x64.zip

@JohnGalt1717
Copy link
Author

Per Damian Edwards on Twitter that isn't the final build and it did change as of yesterday and the purge will be required.

Excellent find on the actual link. Here's hoping that's actually final. Apparently they were having problems pushing it out, which implies some devops issue but who knows...

@FlorianRainer
Copy link

Is there a new date for the release of 2.1.1 related SDK / Runtime?

The last announcement with date is this: https://github.com/aspnet/Home/wiki/.NET-Core-2.1.1-Early-Access-Downloads (June 19th)

@JohnGalt1717
Copy link
Author

Still the same preview.

@Tratcher
Copy link
Member

The 2.1.1 deployment is still in progress, please use 2.1.0 in the meantime.

@FlorianRainer
Copy link

Any predictions? Today, Tomorrow, in a Week?
It's because i'm on the way to port 2.0 to 2.1 and the plan was to wait and to use 2.1.1, now it depend on the estimated release date

@RichardD2
Copy link

Looks like it's out now:

Damian Edwards:
#dotnetcore 2.1.1 SDK download is now live!! Thanks everyone for your patience as we worked through the deployment issues the last few days
https://twitter.com/DamianEdwards/status/1009932641460580352

@JohnGalt1717
Copy link
Author

Woot!

@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants