ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #blazor
Learn how Blazor Server keeps component state on the server, syncs UI via SignalR, and what that means for bandwidth, latency, and scalability. A step‑by‑step chat app, trade‑offs, and verification checklist are included.
Learn how to lazy load assemblies in Blazor WebAssembly to cut the initial download size, with a csproj snippet, component example, and common pitfalls to avoid.
Blazor's streaming rendering and enhanced navigation in .NET 8 make server-rendered pages feel like an SPA — progressive HTML delivery, preserved scroll and state, no full reloads. Here's how they work and where the edges are.
An architecture note on Blazor Server's cascading authentication state: why the circuit is the real trust boundary, how AuthorizeView fits in, and the reconnection-after-token-expiry failure mode most designs miss.
Explains how Blazor Interactive Auto provides progressive enhancement, the minimal design, trust boundary shift, operational checks, failure modes, and when to choose a different render mode.
Learn how to use [StreamRendering] in .NET 8 Blazor to eliminate blank screens and improve perceived performance in Static SSR pages.
AOT compilation can strip JavaScript interop calls in Blazor WebAssembly, leaving your C# code with no JavaScript bridge. Here’s how to protect your interop methods and verify they survive the publish pipeline.
Blazor Server keeps component state in a server-side circuit. See how client retry limits and server retention periods interact, and how to verify recovery behaviour.
Learn how to identify why a Blazor Server app shows stale or frozen UI after a brief network drop, diagnose circuit reconnection issues, and apply fixes that preserve scoped state.