In the third week of October 2019, Microsoft announced specific new features in .NET Core 3.1 Preview 1, which is an integral part of the ASP.NET Core component. The reason for this recent update is due to the fact that the first preview release of .NET Core 3.1 had lots of bug fixes of ASP.NET Core. This news was confirmed by Daniel Roth, principal program manager for ASP.NET.
This new preview has resolved this problem. Now, it has an update on Blazor WebAssembly, the client-side part of Blazor, one project that is a hot favorite amongst developers since they are able to utilize C# instead of JavaScript in Web projects.
This is a piece of excellent news for .NET developers since they will now be able to apply ASP.NET application development services without any hassle.
Daniel quoted, “On top of .NET Core 3.1 Preview 1 release, there is a Blazor WebAssembly update that has been released. However, you still need to use the .NET Core 3.1. To maximize the use of Blazor WebAssembly, you need to install .NET Core 3.1 Preview 1 and the latest preview of Visual Studio.”
Let’s now look at the different ASP.NET Core features which are new in .NET Core 3.1 Preview 1.
Partial Class Support for Razor Components
It is now possible to generate razor components in the form of partial classes. Now, it is possible to author the code for a Razor component by employing a code-behind file, which is defined as a partial class. Instead of defining all the code for the component in a single file.
Pass Parameters to Top-Level Components
It is now possible for Blazor Server apps to pass parameters to top-level components when the initial render takes place. Earlier, it was only possible to pass parameters to an essential element with RenderMode.Static. However, after this release, both RenderMode.Server and RenderModel.ServerPrerendered now gets supported. In case, any specific parameter value is being considered, it is possible to serialize it as JSON and integrated it into the primal response.
Support for Shared Queues in HttpSysServer
On top of the prevailing behavior where HttpSysServer creates anonymous request queues, in the recent update, it is possible to integrate the ability to create or attach to a regular named HTTP.sys request queue. This way, there can be conditions where the HTTP.Sys controller process that has the line is autonomous of the listener process. At the end of the day, it assists in preserving existing connections and enqueued requests between across listener process restarts.
Breaking Alterations for SameSite Cookies
Thanks to this release, there is a significant update regarding the behavior of SameSite cookies in ASP.NET Core. It follows the latest standards that are supported by browsers. For more information on the changes and their impact on the existing apps, click here.
Concluding Thoughts
These are some of the new ASP.NET Core features that are present in .NET Core 3.1 Preview 1. To take advantage of this latest feature in ASP.NET web development, get in touch with a reputed ASP.NET development company. For more information, visit this blog.