What problem does it solve? Migrating a legacy Blazor Server application to .NET 8+ requires coordinated changes across the project file, Program.cs, _Host.cshtml, and App.razor, and missing any step (like antiforgery middleware or the blazor.web.js script) causes runtime failures that are hard to diagnose. ## Core Features & Use Cases - Guided step-by-step migration: Walks through updating the TFM, creating Routes.razor, converting _Host.cshtml into an App.razor root component, and replacing AddServerSideBlazor/MapBlazorHub with AddRazorComponents/MapRazorComponents. - Authentication and render mode handling: Migrates CascadingAuthenticationState to the AddCascadingAuthenticationState service and preserves prerendering behavior with InteractiveServerRenderMode options. - Validation checklist and pitfalls: Provides a verification checklist and a table of common pitfalls such as missing UseAntiforgery, leftover blazor.server.js references, and lost circuit options. - Use Case: You have a .NET 7 Blazor Server app using Pages/_Host.cshtml and want to move it to .NET 8 with streaming rendering and enhanced navigation while keeping interactive server rendering. ## Quick Start Ask the agent to convert your Blazor Server project to a Blazor Web App targeting net8.0 and follow the guided migration steps.