convert-blazor-server-to-webapp
FeaturedGuides conversion of a pre-.NET 8 Blazor Server app into a .NET 8+ Blazor Web App. USE FOR: migrating apps that use AddServerSideBlazor and MapBlazorHub to the AddRazorComponents/MapRazorComponents model, converting _Host.cshtml to an App.razor root component, replacing blazor.server.js with blazor.web.js, migrating CascadingAuthenticationState to a service, adopting new Blazor Web App features like enhanced navigation and streaming rendering. DO NOT USE FOR: apps that are already Blazor Web Apps (already use AddRazorComponents and MapRazorComponents), Blazor WebAssembly or hosted Blazor WebAssembly apps (different migration path), apps that should stay on the Blazor Server hosting model without converting, or apps still targeting .NET Framework.
Install
Quality Score: 92/100
Skill Content
Details
- Author
- managedcode
- Repository
- managedcode/dotnet-skills
- Created
- 6 months ago
- Last Updated
- 6 days ago
- Language
- C#
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
blazor
Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices. USE FOR: building interactive web UIs with C# instead of JavaScript; choosing between Server, WebAssembly, or Auto render modes; designing component hierarchies and state. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
aspnet-blazor
Blazor Server, WebAssembly, and United (Auto) with components, interop, and render modes. Covers .NET 8+ Blazor patterns. USE WHEN: user mentions "Blazor", "Blazor Server", "Blazor WASM", "Blazor WebAssembly", "Blazor components", "render modes", "Blazor interop" DO NOT USE FOR: Angular components - use `angular`, React components - use `react`, Svelte - use `svelte`
classic-asp-to-aspnet-mvc
Conventions and a working playbook for porting Classic ASP or Web Forms sites to ASP.NET Core MVC on net10.0: Program.cs composition, controllers and routing, view models, Razor layouts, sections and partial views, wwwroot assets, configuration through validated options instead of raw configuration keys, secrets in user secrets locally and Azure Key Vault in production, Dapper repositories behind Abstractions interfaces, and typed HttpClient services that return models rather than transport objects. Use this skill whenever migrating a Classic ASP, ASP, or Web Forms application to ASP.NET Core MVC, reviewing such a migration, scaffolding the MVC layout for a ported site, or deciding where ported inline logic belongs in the new structure.