After the release of .NET Core .0 earlier this year, Microsoft has now introduced a minor lysed .NET Core 3.1 update. In addition to improving the features introduced in version 3.0, 3.1 is a long-supported version, meaning it will be fully supported over the next three years. Meanwhile, support for version 3.0 will close in March next year.
(Instagram via Neowin)
Unsurprisingly, the change log for .NET Core 3.1 is small. The only new feature is the support for the creation of c?/CLI components for .NET Core in Visual Studio 2019.
Although users still need to install components such as “C? Desktop Deployment” and “C? / CLI Support” to work, and two new templates — the CLI Class Library (.NET Core) and the CLR Empty Project (.NET Core).
Some form controls for Windows applications are also excluded from .NET Core 3.1, which has been replaced by more powerful successors for quite some time, which can break some of the user’s projects.
.NET Core 3.1 Download Address Change log
ASP .NET Core (GitHub) portal
The good news is that Microsoft has provided a table to illustrate the changes that are taking place so that users can adjust accordingly.
Partial class support for Razor components;
Pass parameters to top-level components;
New component label assistant;
The default action to block events in the Blazor app;
Stop the spread of events in the Blazor application;
Details of errors during the development of the Blazor application;
Support for shared queues in HttpSysServer;
Significant changes to the SameSite cookie.
Finally, Microsoft introduced a new version of Blazor WebAssembly, adding support for .NET Standard 2.1 and iOS 13:
Support for .NET Standard 2.1;
Support for static assets at the time of release;
support for iOS 13;
Improve the connector error reporting experience;
Attach to Process debugging for Visual Studio.