convert-blazor-server-to-webapp

Update the target framework, 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() in Program.cs.

Move the HTML shell from _Host.cshtml into App.razor, remove Razor Page directives, replace Component Tag Helpers with HeadOutlet and Routes components using InteractiveServer render mode, change the base href to "/", swap blazor.server.js for blazor.web.js, then delete _Host.cshtml.

The UseAntiforgery middleware is missing from the pipeline. AddRazorComponents registers antiforgery services automatically, but you must explicitly add app.UseAntiforgery() after UseAuthentication and UseAuthorization for form posts to succeed.

The CascadingAuthenticationState component wrapper does not work across render mode boundaries in Blazor Web Apps. Replace it with the service-based approach by calling builder.Services.AddCascadingAuthenticationState() in Program.cs.

Skip conversion if the app already uses AddRazorComponents and MapRazorComponents, is a Blazor WebAssembly app with a different migration path, targets .NET Framework, or should remain on the legacy Blazor Server hosting model with only TFM and package updates.