Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Taking Blazor to Production: WASM Size, Trimming, AOT, Circuit Resources, Reconnection UI and Hosting
Taking Blazor to production means measuring two costs: the first-visit download in WebAssembly (2.3 MB for the Bookstore panel, 4.3 MB with AOT but about six times faster on CPU work) and memory per circuit on the server (about 800 KB on the stock page, with a closed tab kept for three minutes). The post covers trimming and relinking, fingerprinted caching, CircuitOptions, ReconnectModal, a nonce-based Content Security Policy and WebSockets behind Nginx, all with real measurements.
Render Modes in Depth: Static SSR, InteractiveServer, InteractiveWebAssembly, InteractiveAuto and Prerendering
A render mode is set on the component definition, where it is used or for the whole app, propagates to child components, and an interactive component cannot switch to another interactive mode inside; parameters from a Static parent are serialized to JSON in the HTML. We add a WebAssembly quote calculator to the Bookstore panel and show the ChildContent error, a silently dropped EventCallback, turning prerendering off and why everything in .Client is visible in the browser.
What Is Blazor? The Blazor Web App, Render Modes and When to Choose It over Angular or MVC
Blazor lets you write interactive web UI with C# and Razor components, and since .NET 8 a render mode decides where each component runs: Static SSR, Interactive Server, Interactive WebAssembly or Auto. We run the same component in all four modes side by side and show the prerendered output, the SignalR circuit, the 2.2 MB downloaded on the first visit and the Blazor-versus-Angular decision for Bookstore's admin panel with real measurements.