Blazor is a free open-source and cross-platform experimental framework developed by ASP.Net Microsoft that brings C# in any browser without any plug-in. But it is no longer listed as an experimental framework, it is now counted in the .Net core 3. It is considered the finest contemporary development in the .Net world. Blazor allows developers to write optimum UI experiences with the help of C# rather than JavaScript. The blazor framework can make the C# more powerful by turning it into a full-stack development tool. It is employed to develop web UI for clients’ applications using Web assembly support.
Despite being embarked initially as an experimental technology, Blazor is classified into two hosting options: Client-side blazor and server-side blazor. This classification is based on their area of functionality i.e. client-side blazor runs in the browser whereas the server-side blazor runs on the server side though it runs the same kind of code.
Let us acknowledge them in brief-
Client Side Blazor:
This scenario is referred as Blazor WebAssembly and, in this the Blazor App, its relainces, and .Net runtime are downloaded to the browser and the app is pushed directly on the browser UI thread. Also the event management and UI updates transpire within the same process.
Server Side Blazor:
In the Server side blazor, it is directed on the server from an ASP.Net Core app. The Javascript calls, event management, UI updates are managed over a SignalR connection.
Let us take you through the pros & cons of Client Side Blazor(WebAssembly) and Server side Blazor respectively.
Pros of Client side Blazor (WebAssembly)
IE, Edge, Firefox, Chrome, Safari, IOS Safari, Opera Mini, Blackberry Browser, UC Browser, Samsung Internet.