February 18th, 2020

.NET Core February 2020 Updates – 2.1.16, 3.0.3, and 3.1.2

Rahul Bhandari (MSFT)
Rahul Bhandari (MSFT)
Program Manager

Today, we are releasing the .NET Core February 2020 Update. These updates only contain non-security fixes. See the individual release notes for details on updated packages.

NOTE: If you are a Visual Studio user, there are MSBuild version requirements so use only the .NET Core SDK supported for each Visual Studio version. Information needed to make this choice will be seen on the download page. If you use other development environments, we recommend using the latest SDK release.

Getting the Update

The latest .NET Core updates are available on the .NET Core download page. This update will be included in a future update of Visual Studio.

See the .NET Core release notes ( 2.1.16 | 3.0.3 | 3.1.2 ) for details on the release, including issues fixed and affected packages.

Docker Images

.NET Docker images have been updated for today’s release. The following repos have been updated.

Note: You must pull updated .NET Core container images to get this update, with either docker pull or docker build –pull.

Category
.NET

Author

Rahul Bhandari (MSFT)
Rahul Bhandari (MSFT)
Program Manager

I am a Program Manager on .NET team. I specializes in .NET release processes. University of Florida Alumnus.

14 comments

Discussion is closed. Login to edit/delete existing comments.

Newest
Newest Popular Oldest
  • Steve Hueners

    From a current win 10 box I’ve run both the hosting bundle and the .NET Core Runtime 3.1.2 but dotnet –version still reports 3.1.101. I even went so far as to -gasp- reboot. The installers are unequivocally reporting success. Subsequent attempts have offered ‘repair’ so at least part of the install is recognizing 3.1.2.

  • Dean Jackson

    Is it possible to prevent the creation of the “runtimes” folder in the output folder (netcoreapp3.0 for me since I’m using Core 3.0) when building/compiling an ASP.Net Core app within Visual Studio? The runtimes folder has subfolders like Unix that I don’t need. I understand the purpose of Core is to run multi-platform, but if you are only going to create Core apps for Windows x64, can you prevent this folder?

    Read more
      • Dean Jackson

        I want to save some disk space when building/compiling, but thanks anyway. Publishing/deployment is a different thing which doesn’t help when building. It doesn’t make sense that the extra Unix folder would get created during build, instead it should get created if I try to publish to a Unix machine.

      • Daniel Lo Nigro

        If you use dotnet build -r windows-x64 then it should only produce Windows artifacts. Not sure where the equivalent setting is in Visual Studio.

  • Me Gusta

    Out of curiosity, what are the plans for Windows ARM64 support?

  • Rajasekar Shanmugam

    Our build systems are down due to an update of Microsoft.AspNetCore.Identity.EntityFrameworkCore to version 3.1.2, but dependent package Microsoft.EntityFrameworkCore.Relational does not have the version 3.1.2 yet on nuget. Are these packages on the way too?

    • Tom Gruszowski

      Looks like it’s fixed, re-update packages

      • Rajasekar Shanmugam

        Thank you Tom. Yay !!! All our services in 3.1.2 ! Awesome.

  • Ion Sorin Torjo

    I don’t understand – why did .netcore 2.2 reach EOL on 2019.12.2023, and .netcore 2.1 will reach EOL on 2021.08.21?

    Basically, I would really not care if I could use .netcore 3.1 on UWP – but can I?

    later edit: apparently UWP still relies on .netcore runtime 2.2 – so how come this reached EOL 2 months ago?

    • Codest

      .NET Core 2.1 is a long-term support (LTS) release. This means that it is supported for three years.

      • cheong00

        It’s kind of puzzling why Microsoft don’t make .NET Core 2.2 LTS instead.

        I thought it’s common practice to make the final minor version release of a major version LTS, so people who prefer to stay in that major version won’t need to choose between “losing improvements from the LTS to the current version they’re using” or “missing security patch for vulnerability discovered after your minor version goes EOL”.

  • Rob Arthur

    We're seeing issues installing 2.1.16 on ubuntu 16.04. Were there some bad dependencies published?

    <code>

    Read more

Read next