consolidate tooling

Author: twsouthwick

.openpublishing.redirection.json

@@ -987,7 +987,17 @@
         },
         {
             "source_path": "aspnetcore/migration/proper-to-2x/mvc2.md",
-            "redirect_url": "migration/mvc/",
+            "redirect_url": "migration/fx-to-core/areas/mvc/",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/mvc.md",
+            "redirect_url": "migration/fx-to-core/tooling",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/web_forms.md",
+            "redirect_url": "migration/fx-to-core/tooling",
             "redirect_document_id": false
         },
         {

aspnetcore/migration/mvc.md

@@ -0,0 +1,53 @@
+---
+title: Learn to upgrade from ASP.NET MVC, Web API, and Web Forms to ASP.NET Core
+description: Learn how to upgrade ASP.NET Framework MVC, Web API, or Web Forms projects to ASP.NET Core using migration tooling
+author: rick-anderson
+ms.author: riande
+ms.date: 06/20/2025
+uid: migration/tooling
+---
+# Use tooling to help migrate ASP.NET Framework to ASP.NET Core
+
+:::moniker range=">= aspnetcore-7.0"
+
+This article shows how to upgrade ASP.NET Framework applications (MVC, Web API, and Web Forms) to ASP.NET Core using the Visual Studio [.NET Upgrade Assistant](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant) and the [incremental update](xref:migration/fx-to-core/inc/overview) approach.
+
+
+   > [!WARNING]
+   > There is a Copilot-enabled tool for staying current on modern .NET, but is not currently enabled for migrating ASP.NET Frameworkt to ASP.NET Core. Please see the documentation for [GitHub Copilot app modernization - Upgrade for .NET]> (https://learn.microsoft.com/en-us/dotnet/core/porting/github-copilot-app-modernization-overview) for details.
+
+## Prerequisites
+
+If your .NET Framework project has supporting libraries in the solution that are required, they should be upgraded to .NET Standard 2.0, if possible. For more information, see [Upgrade supporting libraries](xref:migration/fx-to-core/inc/start#upgrade-supporting-libraries).
+
+
+1. Install the [.NET Upgrade Assistant](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant) Visual Studio extension.
+1. Open your ASP.NET Framework solution in Visual Studio.
+1. In **Solution Explorer**, right click on the project to upgrade and select **Upgrade**. Select **Side-by-side incremental project upgrade**, which is the only upgrade option.
+1. For the upgrade target, select **New project**.
+1. Name the project and select the appropriate template:
+
+   > [!NOTE]
+   > **For MVC projects:** Select **ASP.NET Core MVC** template.
+   > 
+   > **For Web API projects:** Select **ASP.NET Core Web API** template.
+   > 
+   > **For MVC + Web API projects:** Select **ASP.NET Core MVC** template.
+   > 
+   > **For Web Forms projects:** Select **ASP.NET Core** template.
+
+1. Select **Next**
+1. Select the target framework version and then select **Next**. For more information, see [.NET and .NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
+
+   > [!NOTE]
+   > **For Web Forms projects:** Select **Done** instead of **Next**, then proceed to step 9.
+
+1. Review the **Summary of changes**, then select **Finish**.
+1. The **Summary** step displays **`<Framework Project>` is now connected to `<Framework ProjectCore>` via Yarp proxy.**
+
+   > [!NOTE]
+   > **For MVC and Web API projects:** The summary includes a pie chart showing the migrated endpoints. Select **Upgrade Controller** and then select a controller to upgrade. Select the component to upgrade, then select **Upgrade selection**.
+
+:::moniker-end
+
+[!INCLUDE[](~/migration/mvc/includes/mvc6.md)]