Running ASP.NET Core Apps without a server? WHAT???
summary
Claim: you can run full ASP.NET Core apps without a traditional server by compiling C# to WebAssembly with Blazor WebAssembly and shipping the generated static bundle (the demo uploads 126 files including the .NET wasm runtime and blazer.webassembly.js). The workflow uses the Mono runtime, optional AOT and hot reload, and deploys to Azure static website or GitHub Pages via GitHub Actions; demos show the pages serving and interacting in the browser and .NET 8 adds server‑side rendering for SEO.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:04Web app development evolution
- 9:51JavaScript frameworks rise
- 13:26ASP.NET Core limitations
- 16:16Introducing Blazor
- 21:13WebAssembly enables Blazor
- 24:03Blazor vs JavaScript
- 26:54Blazor key features
- 28:40Hosting Blazor without server
- 36:21Deploying to GitHub Pages
- 41:54Blazor server-side rendering
- 45:27Blazor future possibilities
related talks
56mASP.NET Blazor—the C# Angular or the return of Silverlight?
29mBringing WebAssembly to the .NET Mainstream
01h 00mASP.NET Blazor programming 101
41mBlazor, a New .NET Single Page Application Framework
01h 01mBlazor: Modern Web development with .NET and WebAssembly
58mIntro to Blazor, WebAssembly and Razor in .Net
30mSPA Revolution with WebAssembly and ASP.NET Blazor
09mBlazor with WebAssembly
