Before starting talking about Blazor, you need to know that I developed a lot of applications in the .NET Platform, like desktop applications, web, mobile, and also windows services.
I invite you to know my history working with the .NET platform clicking here.
I, as a .NET developer and C# specialist, after the MVP Conf LATAM 2019 event, and watched both Alexandre Malavasi’s and Antonio Maniero’s lectures, I decided to talk about Blazor, the SPA of the .NET Platform.
I am going to try to be more objective as possible, expressing my opinion as a mortal software developer.
# Before Blazor
When I started programming with the .NET Platform, I used WebForms dragging and dropping controls (TextBox, Dropdownlist) on a web page (ASPX) from the Visual Studio’s controls toolbox.
After that, Microsoft introduced other technologies like ASP.NET MVC, another developing design pattern that had separated frontend from business logic.
My point is: now, the Microsoft announces Blazor, where you develop in C# and let Blazor do the dirty work to make it work on all web browsers.
I know that Blazor is more than that, but did you realize what is going on? Sit, down, sit, down.
# Blazor, what we need to start?
Do you want to start programming with Blazor? So, get ready to install ASP.NET CORE 3.0 and some Blazor Visual Studio 2019 extensions.
For those that already work with ASP.NET MVC and Razor Views, it is going to be a piece of cake.
To start with Blazor, add a new ASP.NET CORE web application and chose the Blazor template from Visual Studio 2019.
There are two types of Blazor web applications, one of them is Blazor WebAssembly, still in the preview version.
When your Blazor web application starts for the first time, the web browser downloaded all DLLs and, after that, your web application runs in the browser.
But now the web browser understands C# DLLs?
Is it install the .NET framework in the user’s machine?
Do we need to install an extension to make it work?
And about my jQuery?
Take it easy.
If you want to start developing with Blazor now and don’t want to use the Blazor Web Assembly preview, you can choose the other type of Blazor web application, the Blazor Server App.
Blazor Server App runs at the server-side and uses SignalR to communicate between the web browsers. Amazing!
var text = await JsRuntime.InvokeAsync<string>("ConvertArray", QuoteArray);
# ASP.NET and #C# everywhere
Is Microsoft trying to dominate all development platforms?
# But and about Angular, VueJS and React?
In my opinion, these guys will create some functionality to work with Web Assembly and, the fight for Single Page Applications will rise.
# Blazor: the past, present, and future.
The fact is that Blazor is already a reality.
The future only the Bidus know about it, but we can bet that Blazor will only rise with the .NET community helping it. And distinct, a significant investment, documentation and, publicity from Microsoft.
That’s all for now. Thank you for reading it.