migrating-spa-services-to-spa-proxy

Automate ASP.NET Core migration from SpaServices.Extensions to SpaProxy for Angular and React.

19|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-spa-services-to-spa-proxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-spa-services-to-spa-proxy
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-spa-services-to-spa-proxy
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-spa-services-to-spa-proxy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers migrate their ASP.NET Core projects from the obsolete Microsoft.AspNetCore.SpaServices.Extensions to the more modern Microsoft.AspNetCore.SpaProxy, streamlining the transition and improving performance.

Core Features & Use Cases

  • Migration Automation: Automates the process of updating Startup.cs, project files, and launchSettings.json to integrate SpaProxy.
  • Framework Support: Supports both Angular and React frontends.
  • Use Case: Ideal for projects where Microsoft.AspNetCore.SpaServices.Extensions has been deprecated and must be replaced.

Quick Start

Run the 'migrating-spa-services-to-spa-proxy' skill to start the migration process for your project.

Frequently Asked Questions about migrating-spa-services-to-spa-proxy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from SpaServices to SpaProxy in an ASP.NET Core project?

To migrate from SpaServices to SpaProxy, you need to update your project files, Startup.cs, and launchSettings.json. This process replaces the obsolete Microsoft.AspNetCore.SpaServices.Extensions package with Microsoft.AspNetCore.SpaProxy for improved performance.

What is the difference between SpaServices and SpaProxy for ASP.NET Core?

SpaProxy is the modern replacement for the deprecated SpaServices.Extensions package in ASP.NET Core. Migrating to SpaProxy streamlines frontend integration and improves development server performance for Single Page Applications.

Can I use the SpaProxy migration process for both Angular and React frontends?

Yes, the SpaProxy migration supports both Angular and React frontends. It automates updating the necessary project configurations to ensure your SPA integrates smoothly with ASP.NET Core.

Do I need Node.js installed to migrate my ASP.NET Core SPA to SpaProxy?

Yes, Node.js is required to migrate your ASP.NET Core SPA to SpaProxy. You also need the specific build tools associated with your frontend framework, such as Angular or React, installed in your development environment.

Which ASP.NET Core configuration files are updated when migrating to SpaProxy?

Migrating to SpaProxy updates your project files, Startup.cs, and launchSettings.json. These modifications are necessary to remove the deprecated SpaServices package and configure the new proxy setup.