Articles
ASP.NET Core Dev Team Launches 'Blazor United' Push for .NET 8
Shortly after Blazor creator Steve Sanderson wowed web-devs with a new prototype project called Blazor United and solicited feedback on its viability, Microsoft flipped the switch and put it on the roadmap for .NET 8. His latest pet project (which is how Blazor got started years ago) seeks to unify disparate components of the ASP.NET Core ecosystem to form a new tooling framework, borrowing tech from Razor Pages, MVC, CSHTML and the Blazor Server and client-side Blazor WebAssembly components.
Sanderson nine days ago unveiled Blazor United in a YouTube video titled "Blazor United prototype," wherein he summarized his project: "We've started some experiments to combine the advantages of Razor Pages, Blazor Server and Blazor WebAssembly all into one thing, so this would be a way for Blazor components to be a single architecture for all your web UI scenarios -- that's for plain HTML rendering and for full interactivity either server-side or on WebAssembly -- and that's all in one project with the ability to easily switch between different rendering modes and even mix them in the same page." (See the Visual Studio Magazine) article, "Steve Sanderson Wows Web-Devs with Peek at 'Blazor United' for .NET 8.")
In the video, described as "A quick peek at some of the cool Blazor prototypes we're experimenting with for .NET 8," he also asked for feedback on whether Blazor United seemed relevant to developers and what their scenarios and priorities would be. He further said the team was serious about doing something at least like Blazor United for .NET 8, coming in November.
Feedback was received -- "it's good" -- and now Blazor United is in the ASP.NET Core Roadmap for .NET 8.