This morning I was browsing my Twitter feed and I suddenly woke up reading that Blazor is now an official preview. It was by chance more than one year ago that I stumbled upon Steve Sanderson’s blog post on Blazor. At that time the idea of running C# in the browser was more or less a very crazy endeavor of a small group of people. Since then I am constantly blogging about Blazor and most of my conference talks during the last 12 months were focused on Blazor. Right now I am very happy that the idea of running C# in the browser is going towards global availability. Let’s take a few minutes to look into some key points from yesterday’s announcement.
Few months back I was blogging about the different namings of virtually the same product that we were able to run in two different hosting models: client side and server side. So we had “Blazor” as the name for the client side hosting model and “Razor Components” for the server side hosting models. A key difference was that the server side hosting model is in preview since January. The good news is that naming can be simplified now since Blazor is in official preview. Hence, Microsoft decided to drop the name ASP.NET Core Razor Components, and return to the name Server-side Blazor instead.
This emphasizes that Blazor is a single client app model with multiple hosting models:
- Server-side Blazor runs on the server via SignalR
- Client-side Blazor runs client-side on WebAssembly
… but either way, it’s the same programming model. The same Blazor components can be hosted in both environments.
Also, since Blazor is now part of .NET Core, the client-side Blazor package versions now align with the .NET Core 3.0 versions. For example, the version number of all the preview packages is now
I see this as a sign that Blazor is a real community driven product since this was a real key point of all community feedback the Blazor team received recently.
Another sign that Blazor is heavily community drive is the fact that Telerik, DevExpress, and Syncfusion have joined in the fun and shipped previews of Blazor UI components. This means that we’re now able to use these third party components like we are used to do in Angular or WPF applications.
There are some exciting times ahead of us in the .Net ecosystem. Starting now getting started with Blazor is not only a hobbyist’s thing anymore but a thing that should be taken into consideration by all developers in the .NET ecosystem.
How useful was this post?
Click on a star to rate it!
Average rating / 5. Vote count:
Latest posts by Dan Patrascu-Baba (see all)
- Configuration and environments in ASP.NET Core - 25/11/2019
- GraphQL in the .NET ecosystem - 19/11/2019
- A common use case of delegating handlers in ASP.NET API - 12/11/2019