Blazor is a .NET frontend web framework that supports both server-side rendering and client interactivity in a single programming model

It creates rich interactive UIs using C#

It share server-side and client-side app logic written in .NET.

It render the UI as HTML and CSS for wide browser support, including mobile browsers.

Blazor apps are based on components. A component in Blazor is an element of UI, such as a page, dialog, or data entry form.

The component class is usually written in the form of a Razor markup page with a .razor file extension.

Components in Blazor are formally referred to as Razor components, informally as Blazor components. Razor is a syntax for combining HTML markup with C# code designed for developer productivity.

Blazor Server

Blazor Web Assembly

Blazor Hybrid

All of the above

Wrapper Assembly

Web Assembly

None of the above

Component-based architecture

DI (Dependency Injection)

Blazor Forms and Validation

Live Reload

JavaScript interop

Unit Testing

Blazor apps can be configured to use Blazor Server as hosting model where the Blazor application runs on the server and updates the user interface over a SignalR connection.

Blazor Server apps run on the server, and the user interface is rendered on the server. User interactions are sent back to the server over a real-time SignalR connection.

It's ideal for applications where the logic is better suited for the server side or when you need to minimize the client-side resources.

Blazor WebAssembly (WASM) is a client-side hosting model of the Blazor framework that enables developers to build interactive web applications using C# and .NET technologies. Unlike Blazor Server, which runs on the server and relies on SignalR for real-time communication, Blazor WebAssembly applications run entirely in the client’s browser using WebAssembly (WASM).

The Blazor application and the .NET runtime are compiled into WebAssembly (WASM) bytecode.

When a user navigates to a Blazor WebAssembly application, the browser downloads the necessary WASM binaries, .NET runtime, and application assets (HTML, CSS, JS, and DLL files).

The WebAssembly bytecode runs directly in the client’s browser, which provides a virtual environment for executing .NET code. This includes the .NET runtime and application logic.

Microsoft Edge

Mozilla Firefox

Google Chrome, including Android

Safari, including iOS

Microsoft Internet Explorer

dotnet new blazorserver -o WebApplication1
cd WebApplication1
dotnet run

dotnet blazorserver -o WebApplication1
cd WebApplication1
dotnet run

dotnet blazorserver new -o WebApplication1
cd WebApplication1
dotnet run

None of the above

dotnet new blazorwasm -o WebApplication1
cd WebApplication1
dotnet run

dotnet new blazorserver -o WebApplication1
cd WebApplication1
dotnet run

dotnet blazorwasm -o WebApplication1
cd WebApplication1
dotnet run

None of the above