Microsoft Releases .NET Core 3.1 And ASP.NET Core 3.1
Microsoft has released ASP.NET Core 3.1, a relatively minor update following the major release of ASP.NET Core 3.0 earlier this year. This release aims to fix any issues and make more improvements to features introduced in dotnet core 3.0, and because of that, it's also a long-term supported release, which means it will be supported for the next three years. dotnet core 3.0 will only be supported until March of next year.
As expected, the change log is fairly small for this release.
The only new addition in .NET Core 3.1 is support for creating C++/CLI
components that target .NET Core in Visual Studio 2019, though you'll need to
install the “Desktop improvement with C++" outstanding burden and the "C++/CLI support" part for it to work. This will also add two new templates - CLR Class
Library (.NET Core) and CLR Empty Project (Core 3.0).
This release of .NET Core is, as usual, accompanied by a new
version of ASP.NET Core and EFCore. Microsoft
provided a short list of changes in ASP.NET Core:
ü
Partial class support for Razor components
ü
Pass parameters to top-level components
ü
New component tag helper
ü
Prevent default actions for events in Blazor
apps
ü
Stop event propagation in Blazor apps
ü
Detailed errors during Blazor app development
ü
Support for shared queues in HttpSysServer
ü
Breaking changes for SameSite cookies
Finally, there's also a new
release of Blazor WebAssembly to go along with this. It adds support for .NET
Standard 2.1 and iOS 13, among other things:
ü
NET Standard 2.1 support
ü
Support for static assets in when publishing
ü
iOS 13 support
ü
Better linker errors
ü
Attach to process debugging from Visual Studio
You can learn more about what's
changed in .NET Core 3.1 as well as ASP.NET Core on GitHub. You can download
.NET Core 3.1 from here.
Post A Comment:
0 comments: