Start Debugging

Tag: blazor

26 posts · Page 2 of 3

2026-08-06 errors blazor aspnetcore

Fix: Attempting to reconnect to the server after a Blazor Server circuit disconnects

The reconnect modal means the SignalR circuit dropped, not that your app crashed. Decide whether the retry ended in failed or rejected, then fix sticky sessions, the 3-minute retention window, the 32 KB message limit, or persist circuit state with [PersistentState].

2026-08-02 csharp dotnet dotnet-11

How to run CPU-bound work in a Blazor WebAssembly app with Web Workers in .NET 11

A complete guide to offloading CPU-bound work off the Blazor WebAssembly UI thread in .NET 11: why Task.Run does not help, the new blazorwebworker template, the WebWorkerClient API with cancellation and timeouts, the JSExport marshalling limits, and the second-runtime cost you pay per worker.

2026-07-30 errors blazor dotnet

Fix: JavaScript interop calls cannot be issued at this time (Blazor prerendering)

Prerendering runs your component on the server with no browser attached, so IJSRuntime throws. Move the call into OnAfterRenderAsync, gate it on RendererInfo.IsInteractive, or disable prerendering.

2026-06-16 blazor dotnet-11 aspnetcore

Blazor static SSR gets [SupplyParameterFromSession] in .NET 11 Preview 5

Reading session state in static server-rendered Blazor meant reaching into HttpContext.Session and serializing by hand. .NET 11 Preview 5 adds [SupplyParameterFromSession] so a component property binds to a session key directly.

2026-06-11 blazor dotnet-11 aspnetcore

Blazor static SSR forms get client-side validation in .NET 11 Preview 5

Static server-rendered Blazor forms could only validate after a full POST round-trip. .NET 11 Preview 5 renders validation metadata so the Blazor JS enforces DataAnnotations rules in the browser, no circuit required.

2026-06-09 errors blazor dotnet

Fix: its render mode is not supported by the parent component's render mode (Blazor)

You put @rendermode on a child whose parent is already interactive. A subtree has exactly one render mode. Remove the child directive or move it to the boundary.

2026-06-09 blazor dotnet-11 aspnetcore

How to persist state across the Blazor static-to-interactive render boundary in .NET 11

A prerendered Blazor component runs its initialization twice and loses state at the interactive handoff. Fix it with the [PersistentState] attribute or the PersistentComponentState service in .NET 11.

2026-06-05 migration blazor dotnet

Migrate a Blazor Server app to Blazor United (Blazor Web App) in .NET 11

A step-by-step checklist to move a standalone Blazor Server app to the unified Blazor Web App template on .NET 11, keeping every page on InteractiveServer with zero behaviour change.

2026-05-26 comparison blazor dotnet

Blazor Server vs Blazor WebAssembly vs Blazor United in .NET 11: which should you pick in 2026?

For any new Blazor app on .NET 11, scaffold a Blazor Web App (the template formerly nicknamed Blazor United) and pick render modes per page. Server-only and WebAssembly-only templates only still make sense in narrow cases.

2026-05-12 errors csharp dotnet

Fix: RZ10012: Found markup element with unexpected name in Blazor

Blazor's Razor compiler emits RZ10012 when a PascalCase tag has no matching component type in scope. Add @using for the component's namespace in _Imports.razor, or @namespace in the component, then rebuild.