Included fixes address security issues detailed in the release notes.
If you are a Visual Studio customer, please read the note included in the Release Notes regarding which SDK is supported by your version of Visual Studio.
.NET Core 2.1.10 and .NET Core SDK 2.1.506
Release Notes
Download 2.1
.NET Core 2.2.4 and .NET Core SDK 2.2.106
Release Notes
Download 2.2
Please report any issues you find with these releases, either responding to this issue, creating a new issue here or creating a new issue in one of the following repos:
Microsoft support policies are defined in the following documents:
@leecow Hi I am Mac user, just went to the download page and I am wondering why mac does not have 2.2.203 only 2.2.106?
I am quite new to .Net Core, does it mean that as long as it's 2.2.4, the SDK version does not matter?
and on this page https://dotnet.microsoft.com/download it's also 2.2.106
@leecow be advised, the "Blog Post" link in https://github.com/dotnet/core/blob/master/release-notes/2.2/2.2.4/2.2.4.md#changes-in-224 forwards to
https://devblogs.microsoft.com/dotnet/net-core-march-2019/
Should be :
https://devblogs.microsoft.com/dotnet/net-core-april-2019-updates-2-1-10-and-2-2-4/
@fschlaef thanks! Fixed: https://github.com/dotnet/core/commit/1b3b626848613320599f945d70a8583dff3ccac1#diff-3fe8fb440ad10bde0667d99db10fa9ce ... in future, feel free to submit PR with the fix ;)
Which SDK do I install if I use both VS 2017 and 2019?
@mattzink - We're going to add some decorations to the download site to help with that information. In the meantime, details are in the release notes. Short answer: 2.1.506 or 2.2.106 for 2017 and 2.1.603 or 2.2.203 for 2019.
@leecow Sorry, I probably wasn't clear. I need to use both VS 2017 and 2019 on the same machine, depending on the project. Should I install both 2.2.106 and 2.2.203 SDKs?
I'll add another question : I accidentally downloaded and installed 2.2.203 but I use Visual Studio 2017, however everything seems to be working just fine.
Can I keep it like this or should I install 2.2.106 instead ?
What are the differences between the two versions ?
@fschlaef It seemed to be working for me as well on my dev machine (version 2.2.202), but on Team City I've got MSBuild compatibility error like this:
Version 2.2.202 of the .NET Core SDK requires at least version 16.0.0 of MSBuild. The current available version of MSBuild is 15.6.82.30579. Change the .NET Core SDK specified in global.json to an older version that requires the MSBuild version currently available.
Then found this 2.2.1XX (for VS 2017) vs 2.2.2XX (for VS 2019) difference and went with 2.2.1XX train.
@mattzink and @nprokopic - It looks like VS on Windows has a bit of a safety buffer for this issue in most cases though, as pointed out, there are some scenarios where MSBuild compat will come up.
@fschlaef - the key differences are lower level tooling updates; compilers, MSBuild and NuGet being the key components.
The download link for aspnetcore on linux-x64 is broken
https://dotnet.microsoft.com/download/dotnet-core/2.1 ->
https://dotnet.microsoft.com/download/thank-you/dotnet-runtime-2.1.10-linux-x64-asp.net-core-runtime-binaries ->
https://download.visualstudio.microsoft.com/download/pr/5967af9f-21d4-4b2f-a166-52af457d02aa/713e9a0f3753cf79171594bbdb92ad89/aspnetcore-runtime-2.1.10-linux-x64.tar.gz ->
Runtime Error
@dhuyvett - I just tried all of the 2.1 asp links and things seem to be working ok. Try again?
@leecow : confirmed that it is working now.
It seems like this is not yet available on the ubuntu feed:
root@0b03e44d6b70:/# apt-cache madison dotnet-sdk-2.1
dotnet-sdk-2.1 | 2.1.603-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.602-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.505-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.504-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.503-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.502-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.500-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.403-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.402-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.401-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.400-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.302-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.301-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
dotnet-sdk-2.1 | 2.1.300-1 | https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages
Is there always a delay? Is there a .deb available somewhere to install it manually?
@matthid - this was a communication error on our part. The ever growing list of versions is making the story very hard to tell. The latest SDKs released for Linux are 2.1.603 and 2.2.203.
@vivmishra @jamshedd
Fully replaced by #2727