ASP.NET Core Starts Path to Hot Reload, AoT Compilation, Blazor Desktop, More
The first preview of .NET 6 arrived with grand plans for ASP.NET Core — the web-dev component — including much-requested features like hot reload, ahead-of-time (AoT) compilation and the beginnings of Blazor hybrid desktop projects.
Developers need to wait a while for all those goodies, though, as EF Core 6 will debut with parent framework .NET 6 in November as part of long-term release (LTS) that combines formerly separate components into one unifying umbrella platform, and Preview 1 only sports minor features such as:
- Support for
ElementReferenceexposed on relevant components
dotnet watchnow does
dotnet watch runby default
- Nullable reference type annotations
The list of those aforementioned goodies, however, was presented as a raft of GitHub issues:
That effort stems from an Oct. 26, 2020, issue summarized like this: “In .NET 6 we want to extend Blazor’s target scenarios to include native desktop applications via web-based rendering.”
One developer quick to jump on the Blazor desktop bandwagon was Sam Basu, Progress Developer Advocate for Telerik products, who penned a blog post about it yesterday, when .NET 6 Preview 1 was announced.
He pointed out two ways to create Blazor desktop apps: wrapped in an Electron shell or by extending Blazor Mobile Bindings, which is based on Xamarin.Forms, Microsoft’s mobile development framework that is in the process of evolving into .NET MAUI.
The first method, using Electron, requires the bundling of the Chromium engine and the Node.js runtime, making for a hefty package.
Blazor guru Steve Sanderson, though, examined ways to lessen the load way back in 2019, while presenting the WebView method.
“It does beg the question as to whether lighter web shells could do the job of hosting modern Blazor apps with a level of consistency,” Basu said of Sanderson’s post. “Time will tell, but thankfully there are some alternatives to play around with.”
Developers can track the development of those alternatives and ASP.NET Core itself by peeking into Microsoft’s open planning process for .NET 6 via GitHub issues presented in the Themes of .NET site — where development efforts are tracked — and the ASP.NET Core 6 Roadmap. (Ironically, the Blazor-powered Themes of .NET site is down as this is being written, perhaps not a good look for Microsoft.)