ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #blazor
Make Blazor Server survive transient network loss with automatic circuit reconnection, visible reconnect UI, persisted state, and safe fallbacks for permanent disconnects.
Learn how Blazor WebAssembly’s ‑pwa flag scaffolds a service worker, what assets get cached, and how to verify offline functionality. A step‑by‑step example shows bundle impact, trade‑offs, and how to customize caching.
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.
Optimize Blazor WebAssembly startup times by deferring heavy assemblies. Learn how to use BlazorWebAssemblyLoadOnDemand to reduce initial payload size.
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 applications need to keep form validation state when users leave a page or refresh, so that error messages and field statuses reappear on return. The difficulty is choosing a storage location—client‑side storage such as sessionStorage, a scoped service, or a cascading value—that survives component disposals without leaking memory. Asynchronous validat
Developers building Blazor Server apps often notice slower UI updates under load but lack a systematic way to pinpoint whether the delay originates from component rendering, SignalR circuit latency, or JavaScript interop. The goal is to establish a repeatable measurement process that isolates each layer while respecting constraints such as production‑like tr
When a Blazor WebAssembly app shows slow UI response, what systematic approach can be taken to pinpoint the cause using only the framework’s built‑in diagnostics and browser developer tools? Enable Blazor’s built‑in performance counters by setting blazor.enablePerf=true in the app’s configuration or via query string. Record a trace with the Chrome Performanc
Goal: reconcile Blazor Server circuit lifecycle events with reverse proxy WebSocket timeout behavior to maintain persistent connections without unnecessary disconnections. Constraint/uncertainty: SignalR's KeepAliveInterval and AutoDisconnectTimeout are calculated on the client-side circuit handler, but when an intermediate proxy or load balancer terminates
dotnet