What Is Blazor WebAssembly and How Does It Work?

The Blazor web framework allows Razor components to be hosted in different ways. They can run server-side in ASP.NET Core (Blazor Server) and client-side in the browser on a WebAssembly-based .NET runtime (Blazor WebAssembly or Blazor WASM).

In the client-side model (Blazor WebAssembly), the Blazor app, its dependencies and the .NET runtime are downloaded to the browser and the app is executed directly on the browser UI thread. All UI updates and event handling happen within the same process.

The Blazor WASM hosting model offers several benefits:

• Run Blazor apps offline once downloaded - Blazor WebAssembly apps built as Progressive Web Apps (PWAs) can run offline (for example when clients aren't able to connect to the Internet)
• Static site hosting - Blazor WebAssembly apps are downloaded to clients as a set of static files (no server is required to execute server-side code to download and run)
• Offloads processing to clients (apps are executed on the clients)

Learn how to get started with Blazor WebAssembly in a few easy steps. This article explains how to get the Telerik Blazor components in your Blazor WebAssembly app and start using them quickly. You will create a new application from scratch, learn how to add the UI for Blazor components to a project and finally, add a UI component to a view.

Check the linked article if you want to learn more about Blazor WebAssembly vs Server.