Why should I use blazor ?

Aymen Amri

Dear Community

I'm starting a new project, and we are thinking about using blazor.
It's the first time for me that I use it so before working with any technology I always want to get feedbacks from the experts :).

When I started to go through a small project written in blazor I noticed the following point :
I found in some .razor samples that xml is mixed with the C# code in the same file.
It reminded me the Asp way where everything was mixed in one file without having any code behind or viewModel ...

So my questions are :
   1- what's the advantage of a such implementation ?
   2- how can we ensure the seperation of concerns with this implementation ?
   3- How easy will be the implementation of unit tests for the .razor files ?

The project is a classical one with backend and frontEnd. What are the advantages of blazor compared to other front end technologies

Thanks

6 Replies

Know the answer? Post it — somebody with the same question will find it here.

Nitin Sontakke4y ago
Accepted answer
If at all you go ahead with Blazor path, take the WebAssembly route.
1/ With Blazor all your code base is in just one language, preferably C# and there is no learning curve involved for developers to learn typeScript, javaScript, Angular, React, Vue, etc. This is the BIGGEST plus, I think.
2/ JavaScript interop is available if needed.
3/ Create a SEPARATE class library project for models required to be SENT by WebAPI project and CONSUMED by Blazor project. Then add the reference of this project in BOTH in API project and Blazor project. This way, if you add a property to a class, it is visible to BOTH the layers. A major headache of keeping it in sync is gone.
4/ Code separation is possible. Just create a separate file with .cs extension. What you saw was, of course, just an example.
5/ Use MudBlazor and a complete suite of fully functional components is available to you.
6/ You can make full use of Bootstrap and responsive UI just as in any other front-end framework.
7/ If properly abstracted, your front-end code will look very clean and intuitive to use. In fact, once domain classes are written any junior developer can do MOST of other coding such as data-binding.
8/ MVC like attribute based validation is available, for example [Required]. Much of client side validation is taken care of virtually effortlessly.
Should you need any other input / help, please do get in touch and we take this further.
Aymen Amri4y ago
Hi Sam

In fact, yes our solution is strongly linked to business. It handles purchase transactions, sale transactions account management ....

So you're raising an important point and we need to consider it in our choice.
Nitin Sontakke4y ago
First, Blazor WebAssembly is best suited for web application for wider audiance used over Internet. And Blazor Server is best suited for enterprise application used over Intranet and preferably using Active Directory users and SSO. Notice the words BEST SUITED.

Second, Blazor WebAssembly is similar (please NOTICE the word similar, I obviously know the differences) to front-end frameworks like Angular, etc.

How one would perform CRUD operations in Angular? Not directly, but through WebAPI, right? Blazor WebAssembly works exactly same way.

The typical baggage of separation of concern / single responsibility stuff, you know. Only difference is increasingly the frameworks are now enforcing these things themselves.

Finally, I am not an expert either!
Sam Hobbs4y ago
An important point that I do not see mentioned yet is that Blazor WebAssembly is a single-page app (SPA) framework. A SPA can be very useful but not for everything. Blazor WebAssembly is good for static websites. Blazor WebAssembly can be a mistake for businesses; database access is either insecure or requires more complicated solutiions. See the following.

ASP.NET Core Blazor hosting models | Microsoft Docs
https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-models?view=aspnetcore-6.0#blazor-webassembly

ASP.NET Core Blazor | Microsoft Docs
https://docs.microsoft.com/en-us/aspnet/core/blazor/?view=aspnetcore-6.0

c# - How do you create a Blazor WebAssembly website connected to a database with CRUD functions - Stack Overflow
https://stackoverflow.com/questions/68360161/how-do-you-create-a-blazor-webassembly-website-connected-to-a-database-with-crud

c# - How to connect Blazor WebAssembly to DataBase - Stack Overflow
https://stackoverflow.com/questions/63996294/how-to-connect-blazor-webassembly-to-database

For a business, ASP.Net Core with MVC or Razor Pages might be a better solution. It might take more time to create intitally but might be a better solution for the future.

I am only beginning to learn any of those; I do not claim to be an expert. I am basing what I am saying on what many professional web developers use.

I am reading the book Pro ASP.NET Core 6 by Adam Freeman.
Aymen Amri4y ago
Very clear and detailed.
Thanks a lot
Sachin Singh4y ago
I will say, if you love c# more than Javascript then go for blazor.
else stick with angular/react etc.