Swimburger

Video: How to deploy ASP.NET Blazor WebAssembly to GitHub Pages

Niels Swimberghe

Niels Swimberghe - - .NET

Follow me on Twitter, buy me a coffee

With ASP.NET Blazor WebAssembly (WASM) you can create .NET web applications that run completely inside of the browser sandbox. The publish output of a Blazor WASM project are all static files. Now that you can run .NET web applications without server-side code, you can deploy these applications to various static site hosts, such as Azure Static Web Apps and GitHub Pages.

In this video you learn how to deploy Blazor WASM to GitHub Pages, manually and automatically with GitHub Actions:

 

If you prefer written content, check out my blog post: How to deploy ASP.NET Blazor WebAssembly to GitHub Pages.

Related Posts

See All Posts
See All Posts

Related Posts

How to deploy ASP.NET Blazor WebAssembly to Azure Static Web Apps. Blazor logo pointing to a GitHub logo pointing to an Azure logo.

How to deploy Blazor WASM & Azure Functions to Azure Static Web Apps using GitHub

- .NET
With ASP.NET Blazor WebAssembly you can create .NET applications that run inside of the browser . The output of a Blazor WASM project are all static files. You can deploy these applications to static site hosts, such as Azure Static Web Apps and GitHub Pages.
ASP.NET Blazor Logo

How to run code after Blazor component has rendered

- .NET
Blazor components render their template whenever state has changed and sometimes you need to invoke some code after rendering has completed. This blog post will show you how to run code after your Blazor component has rendered, on every render or as needed.