News

What's New for Blazor and ASP.NET Core in .NET Core 3.1 Preview 2

While the ASP.NET Core team primarily focused on bug fixes in the new .NET Core 3.1 Preview 2, there was a smattering of new functionality introduced in the webdev component.

Here's a rundown of those new features in ASP.NET Core, which includes Blazor to enable .NET-centric Web developers to use C# instead of JavaScript, thanks to WebAssembly.

  • New component tag helper: This is said to ease the use of Razor components from views and pages, which previously required rendering a component from a view or page using the RenderComponentAsync HTML helper. "The new component tag helper simplifies the syntax for rendering components from pages and views. Simply specify the type of the component you wish to render as well as the desired render mode. You can also specify component parameters using attributes prefixed with param-."
  • Prevent default actions for events in Blazor apps: "You can now prevent the default action for events in Blazor apps using the new @oneventname:preventDefault directive attribute."
  • Stop event propagation in Blazor apps: "Use the new @oneventname:stopPropagation directive attribute to stop event propagation in Blazor apps."
  • Validation of nested models in Blazor forms: This experimental feature, presented for early developer feedback rather than inclusion in .NET Core 3.1, improves on the existing built-in DataAnnotationsValidator used to validate form input using data annotations. It can only validate top-level properties of a model bound to a form. "To validate the entire object graph of the bound model, try out the new ObjectGraphDataAnnotationsValidator available in the experimental Microsoft.AspNetCore.Blazor.DataAnnotations.Validation package."
  • Detailed errors during Blazor app development: This helps developers get detailed error information in order to troubleshoot and fix issues. "Blazor apps now display a gold bar at the bottom of the screen when an error occurs. During development, in Blazor Server apps, the gold bar will direct you to the browser console where you can see the exception that has occurred."

All of the above and more is detailed in an announcement post published by program manager Daniel Roth during Microsoft's Ignite conference. More information can be found in the release notes and the GitHub project. Our coverage of the .NET Core 3.1 Preview 2 release also announced today can be found here.

About the Author

David Ramel is an editor and writer for Converge360.

comments powered by Disqus

Featured

  • What's Next for ASP.NET Core and Blazor

    Since its inception as an intriguing experiment in leveraging WebAssembly to enable dynamic web development with C#, Blazor has evolved into a mature, fully featured framework. Integral to the ASP.NET Core ecosystem, Blazor offers developers a unique combination of server-side rendering and rich client-side interactivity.

  • Nearest Centroid Classification for Numeric Data Using C#

    Here's a complete end-to-end demo of what Dr. James McCaffrey of Microsoft Research says is arguably the simplest possible classification technique.

  • .NET MAUI in VS Code Goes GA

    Visual Studio Code's .NET MAUI workload, which evolves the former Xamarin.Forms mobile-centric framework by adding support for creating desktop applications, has reached general availability.

  • Visual Studio Devs Quick to Sound Off on Automatic Updates: 'Please No'

    A five-year-old Visual Studio feature request for automatic IDE updates is finally getting enacted by Microsoft amid a lot of initial developer pushback, seemingly misplaced.

  • First Official OpenAI Library for .NET Goes Beta

    Although it seems Microsoft and OpenAI have been deeply intertwined partners for a long time, they are only now getting around to releasing an official OpenAI library for .NET developers, joining existing community libraries.

Subscribe on YouTube