convert-blazor-server-to-webapp

Update the TFM to net8.0, move the Router from App.razor into a new Routes.razor, convert Pages/_Host.cshtml into an App.razor root component, and replace AddServerSideBlazor/MapBlazorHub with AddRazorComponents().AddInteractiveServerComponents() and MapRazorComponents<App>().AddInteractiveServerRenderMode().

Move the HTML shell from _Host.cshtml into App.razor, remove Razor Page directives and tag helpers, replace the Component Tag Helpers with <HeadOutlet @rendermode="InteractiveServer" /> and <Routes @rendermode="InteractiveServer" />, change blazor.server.js to blazor.web.js, then delete _Host.cshtml.

The antiforgery middleware is missing. AddRazorComponents registers antiforgery services but you must explicitly add app.UseAntiforgery() to the pipeline, placed after UseAuthentication and UseAuthorization.

The <CascadingAuthenticationState> component wrapper does not work across render mode boundaries in Blazor Web Apps. Replace it with builder.Services.AddCascadingAuthenticationState() in Program.cs, which provides authentication state as a cascading value to all components.

Skip conversion if the app already uses AddRazorComponents and MapRazorComponents, if it is a Blazor WebAssembly app (different migration path), if it should stay on the legacy Blazor Server model, or if it still targets .NET Framework.

If the original app used render-mode="Server" instead of "ServerPrerendered", use new InteractiveServerRenderMode(prerender: false) for HeadOutlet and Routes instead of the InteractiveServer shorthand, which enables prerendering.