The .NET 5 will serve as a merger of .NET Framework and .NET Core as it is intended to unify the .NET platform and the new .NET 5 is due for general availability on November 10, 2020.
While Microsoft .NET 5 eighth preview has arrived, almost every feature are now in its stable form, with the exception of some bug fixes.
And the goals for .NET 5 include bringing a unified .NET SDK experience, with a single base class library (BCL) across the .NET 5 applications, and support both native and web applications across multiple operating systems, such as Windows, Microsoft Duo (Android), and Apple iOS via native controls.
What’s new in Microsoft .NET 5
Microsoft .NET 5 include support for faster algorithms in the BCL, better support for containers in the runtime, and support for HTTP3 which are essential for building high-performance cloud applications. It also includes support for WebAssembly binary format via the Mono runtime and .NET libraries.
Along with a set of nullable reference type annotations, other improvements noted in the .NET 5 Preview 8 bulletin, includes:
- Support for Windows ARM64
- More capable JsonSerializer APIs
- Performance improvements in the NET libraries, the GC, and the JIT
- Support for WebAssembly, using the Mono runtime and the .NET Libraries
- Visual Basic is also included in the .NET 5.0 SDK
Additionally, there is the new foundation of Blazor Web Assembly in .NET 5.0, which is a change from Blazor 3.2, using the Mono runtime and Mono libraries. The advantages of this change are a single development experience for .NET, and much higher compatibility between the various .NET app types.
What are the .NET 5 novel changes?
The .NET and Windows teams have all been working hard to change the way WinRT works, replacing WinRT support for Windows with the C#/WinRT toolchain in .NET 5. And C#/WinRT is a NuGet-packaged toolkit to offer WinRT projection support for C#.
And the removal of the built-in support for WinRT (Windows Runtime), a collection of APIs for building Universal Windows Platform applications, is perhaps a breaking change; whereby .NET Core 3.x apps using WinRT must be recompiled.