Announcing .NET 5.0 Preview 3

Avatar

Richard

Today, we’re releasing .NET 5.0 Preview 3. It contains a set of new features and performance improvements. We’re continuing to work on the bigger features that will define the 5.0 release. The .NET 5.0 Preview 1 post covers what we are planning on building for .NET 5.0. Please take a look at the post and the dotnet/designs repository and share any feedback you have. And, of course, please install Preview 3, and test your workloads with it.

You can download .NET 5.0 Preview 3, for Windows, macOS, and Linux:

ASP.NET Core and EF Core are also being released today.

You need to use Visual Studio 2019 16.6 to use .NET 5.0. Install the latest version of the C# extension, to use .NET 5.0 with Visual Studio Code. .NET 5.0 isn’t yet supported with Visual Studio for Mac.

Release notes:

Let’s look at some of the improvements in Preview 3.

Code quality improvements in RyuJIT

Every release includes a set of changes that improve the machine code that the JIT generates (we call this “code quality”). Better code quality means better application performance.

System.Text.Json improvements

.NET SDK Support for .NET Framework Assemblies

The .NET SDK will now auto-reference the Microsoft.NETFramework.ReferenceAssemblies NuGet package given a .NET Framework target framework in a project file. This change enables building .NET Framework projects on a machine without the required .NET Framework targeting pack installed. This improvement is specific to targeting packs, and doesn’t account for other dependencies that a project may have.

Closing

Please take a moment to try out Preview 3, possibly in a container, a VM. We’d like your feedback on the quality of the release. There is a lot more coming, over the next several months, leading up a November release.

22 comments

Comments are closed. Login to edit/delete your existing comments

    • Avatar
      Anthony Irwin

      The short answer is no.

      Microsoft has said from the very first .net 5 announcement that .net 5 is the current .net core rebranded to .net 5 as a clear sign to developers that it is the next .net and the one to be using moving forward. So Microsoft is skipping .net core 4.x and rebranding to .net 5 to show everyone it is the next major release of .net.

      The existing .net framework is for legacy code bases that are not supported in the current .net core technologies and Microsoft said they plan to do maintenance releases for existing .net framework to keep legacy apps working but no new features like c# 8.0 which only works on .net core/.net 5 not on the now legacy .net framework.

  • Avatar
    Clarke Bowers

    What is the plan for Windows.Devices in .NET5. I have not been able to find information on this value namespace’s future. There is support for GPIO, ADC, PWM and other devices within this namespace. It would be valuable to support this across platforms.