ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Architecture note on the Blazor Server circuit model: managing per-circuit state isolation, SignalR trust boundaries, operational checks, and the limits of in-memory state.
Learn how to implement a custom CircuitHandler in Blazor Server to track user connectivity, prevent memory leaks, and customize the reconnection UI for a professional user experience.
Build a minimal yet secure authentication architecture for a Blazor Server app, tying ASP.NET Core Identity, cookie auth, and SignalR together. The guide covers trust boundaries, operational checks, and failure handling.
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.
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.
Make Blazor Server survive transient network loss with automatic circuit reconnection, visible reconnect UI, persisted state, and safe fallbacks for permanent disconnects.
Learn how to build a lean, secure Blazor Server authentication flow using ASP.NET Core Identity, SignalR, and CircuitOptions. The guide covers requirements, a minimal architecture, trust boundaries, operational checks, failure modes, and when to rethink the design.
The yellow 'reconnecting' banner in Blazor Server means the SignalR circuit died. Learn to read the timing, check the _blazor WebSocket, and match fixes—retention tuning, async handlers, proxy timeouts, sticky sessions—to the actual cause.
blazor
dotnet