Migrate a reviewed legacy Blazor WebAssembly client to .NET 10
ProprietaryOpt-in SDK, framework and package conversion of one selected evaluated Blazor 3.2.0/3.2.1 client. Adopt the .NET 10 BlazorWebAssembly SDK and reviewed 10.0.14 packages; remove obsolete build/Razor declarations and the framework-provided HTTP JSON reference. Requires explicit SDK, browser/JavaScript, reference and CI review. Authentication, conditional/imported/central policy and unknown shapes remain manual. Does not install SDKs or change global.json.
OpenRewrite. Recipes. CSharp. Migration. Dotnet. Net10. MigrateReviewedLegacyBlazorClientRequired
Exact repository-relative .csproj path, without globs.
Optional
Confirm .NET 10 SDK availability and review all imports, package and project-reference consumers, browser startup/JavaScript behavior, deployment and CI. Defaults to false.
Restore final project metadata; a composition can defer to its final EnsureCsprojAttestation.
mod run . --recipe= OpenRewrite. Recipes. CSharp. Migration. Dotnet. Net10. MigrateReviewedLegacyBlazorClient \
-P ProjectPath= Client/ Client. csprojInstall it once, then run it on every repository under the current directory. New to the Moderne CLI? Set it up.