migrating-spa-services-to-spa-proxy Skill
Migrates ASP.NET Core projects from the obsolete Microsoft.AspNetCore.SpaServices.Extensions to Microsoft.AspNetCore.SpaProxy for Angular and React SPAs. Use ONLY when Microsoft.AspNetCore.SpaServices.Extensions has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where SpaSe Published by microsoft in upgrade-agent-plugins.
What is migrating-spa-services-to-spa-proxy Skill?
Migrates ASP.NET Core projects from the obsolete Microsoft.AspNetCore.SpaServices.Extensions to Microsoft.AspNetCore.SpaProxy for Angular and React SPAs. Use ONLY when Microsoft.AspNetCore.SpaServices.Extensions has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where SpaSe Published by microsoft in upgrade-agent-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using upgrade-agent-plugins
Technical details
- Install or run with Copy skill directory
When to use migrating-spa-services-to-spa-proxy Skill
- Use it for developers using upgrade-agent-plugins.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-spa-services-to-spa-proxy/SKILL.md
What it does
Migrates ASP.NET Core projects from the obsolete Microsoft.AspNetCore.SpaServices.Extensions to Microsoft.AspNetCore.SpaProxy for Angular and React SPAs. Use ONLY when Microsoft.AspNetCore.SpaServices.Extensions has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where SpaSe
Skill instructions
SpaServices to SpaProxy Migration Overview Migrate ASP.NET Core projects from Microsoft.AspNetCore.SpaServices.Extensions to Microsoft.AspNetCore.SpaProxy. The backend no longer manages the SPA dev server inline via UseSpa(); instead, SpaProxy automatically launches the frontend dev server and proxies requests to it. This removes all SpaServices middleware from Startup.cs and moves configuration to the project file and hosting startup assembly. Covers both Angular and React frontends. Steps are shared unless marked framework-specific. Workflow Migration Progress: - [ ] Step 1: Detect SpaServices usage and identify frontend framework - [ ] Step 2: Update Startup.cs - [ ] Step 3: Update the project file - [ ] Step 4: Update launchSettings.json - [ ] Step 5: Update package.json - [ ] Step 6: Update angular.json (Angular only) - [ ] Step 7: Add HTTPS and proxy configuration files - [ ] Step 8: Build and verify Step 1: Detect SpaServices Usage Scan the project for: - Package references to M
Explore related resources
Frequently asked questions
What is migrating-spa-services-to-spa-proxy?
migrating-spa-services-to-spa-proxy is a open-source AI agent skill with Copy skill directory. Migrates ASP.NET Core projects from the obsolete Microsoft.AspNetCore.SpaServices.Extensions to Microsoft.AspNetCore.SpaProxy for Angular and React SPAs.
Who is migrating-spa-services-to-spa-proxy best for?
migrating-spa-services-to-spa-proxy is best for reusing agent instructions, scripts, and references.
How do I install migrating-spa-services-to-spa-proxy?
Install or run migrating-spa-services-to-spa-proxy using Copy skill directory. Check migrating-spa-services-to-spa-proxy for the latest setup command.
Is migrating-spa-services-to-spa-proxy actively maintained?
migrating-spa-services-to-spa-proxy may need a closer maintenance check before production use.
Auto-fetched from GitHub.
