convert-blazor-server-to-webapp

Update the TFM to net8.0 or later, 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 Pages/_Host.cshtml into App.razor, remove Razor Page directives and Tag Helpers, replace the Component Tag Helpers with HeadOutlet and Routes components using InteractiveServer render mode, then delete _Host.cshtml.

No. Blazor Web Apps use _framework/blazor.web.js instead of _framework/blazor.server.js. All script references must be updated, since the old script does not work with the new hosting model.

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

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

Remove the CascadingAuthenticationState component wrapper around the router and register builder.Services.AddCascadingAuthenticationState() in Program.cs. The component wrapper does not work across render mode boundaries in Blazor Web Apps.