Remove refs to upgrade assist; add ghcp app mod

Author: adegeo

docs/core/porting/framework-overview.md

@@ -2,7 +2,7 @@
 title: Port from .NET Framework to .NET
 description: Understand the porting process and discover tools you might find helpful when porting a .NET Framework project to .NET.
 author: adegeo
-ms.date: 06/03/2025
+ms.date: 09/15/2025
 ms.custom: devdivchpfy22, updateeachrelease
 no-loc: ["package.config", PackageReference]
 ---
@@ -72,13 +72,13 @@ There are a few technologies in .NET Framework that don't exist in .NET:
 
 - [Application domains](net-framework-tech-unavailable.md#application-domains)
 
-  Creating additional application domains isn't supported. For code isolation, use separate processes or containers as an alternative.
+  Creating other application domains isn't supported. For code isolation, use separate processes or containers as an alternative.
 
 - [Remoting](net-framework-tech-unavailable.md#remoting)
 
   Remoting is used for communicating across application domains, which are no longer supported. For simple communication across processes, consider inter-process communication (IPC) mechanisms as an alternative to remoting, such as the <xref:System.IO.Pipes> class or the <xref:System.IO.MemoryMappedFiles.MemoryMappedFile> class. For more complex scenarios, consider frameworks such as [StreamJsonRpc](https://github.com/microsoft/vs-streamjsonrpc) or [ASP.NET Core](/aspnet/core) (either using [gRPC](/aspnet/core/grpc) or [RESTful Web API services](/aspnet/core/web-api)).
 
-  Because remoting isn't supported, calls to `BeginInvoke()` and `EndInvoke()` on delegate objects will throw `PlatformNotSupportedException`.
+  Because remoting isn't supported, calls to `BeginInvoke()` and `EndInvoke()` on delegate objects throw `PlatformNotSupportedException`.
 
 - [Code access security (CAS)](net-framework-tech-unavailable.md#code-access-security-cas)
 
@@ -123,36 +123,30 @@ Instead of manually porting an application from .NET Framework to .NET, you can
 
 Even if you use a tool to help port your application, you should review the [Considerations when porting section](#considerations-when-porting) in this article.
 
-### GitHub Copilot App Modernization – Upgrade for .NET
+### GitHub Copilot app modernization assistant
 
-[GitHub Copilot App Modernization – Upgrade for .NET](github-copilot-app-modernization-overview.md) is a Visual Studio extension that helps you upgrade projects to newer versions of .NET, update dependencies, and apply code fixes. It leverages GitHub Copilot to provide an interactive upgrade experience.
+[GitHub Copilot app modernization](github-copilot-app-modernization-overview.md) is a GitHub Copilot chat assistant helps you plan and upgrade projects to newer versions of .NET, migrate to Azure, update dependencies, and apply code fixes. Azure migration is powered by [Application and code assessment for .NET](../../azure/migration/appcat/app-code-assessment-toolkit.md)
 
-This tool supports the following upgrade paths:
+This chat assistant supports the following upgrade paths:
 
-- Upgrade projects from .NET Core to .NET.
-- Upgrade projects from older versions of .NET to the latest.
-- Modernize your code base.
+- Upgrade projects from older .NET versions to the latest.
+- Upgrade projects from .NET Framework to the latest version of .NET.
+- Modernize your code base with new features.
+- Migrate components and services to Azure.
 
-**When to use:**
-
-Use GitHub Copilot App Modernization – Upgrade for .NET for scenarios where you want to upgrade your .NET project code and dependencies to newer versions of .NET using an AI-powered tool.
-
-### GitHub Copilot app modernization for .NET
-
-GitHub Copilot app modernization for .NET (Preview) helps you migrate .NET applications to Azure efficiently and confidently. Powered by GitHub Copilot and [Application and code assessment for .NET](../../azure/migration/appcat/app-code-assessment-toolkit.md), it guides you through assessment, solution recommendations, code fixes, and validation—all within a single tool.
-
-With this assistant, you can:
+It also works on various project types, such as:
 
-- Assess your application's code, configuration, and dependencies.
-- Plan and set up the right Azure resources.
-- Fix issues and apply best practices for cloud migration.
-- Validate that your app builds and tests successfully.
-
-For more details, see the [GitHub Copilot app modernization for .NET overview](upgrade-assistant-overview.md).
+- ASP.NET and related technologies such as MVC, Razor Pages, Web API
+- Blazor
+- Azure Functions
+- Windows Presentation Foundation
+- Windows Forms
+- Class libraries
+- Console apps
 
 **When to use:**
 
-Use the GitHub Copilot app modernization for .NET (Preview) experience for scenarios where you need end to end assessment, planning, and remediation for migrating your .NET apps to Azure.
+Use GitHub Copilot app modernization when you want an AI-powered, end-to-end experience to upgrade .NET Framework projects and dependencies to modern .NET&mdash;covering assessment, planning, remediation, and guidance for migrating applications to Azure.
 
 ### Application and Code Assessment for .NET
 
@@ -196,7 +190,7 @@ For more information, see [Platform compatibility analyzer](../../standard/analy
 
 When porting your application to .NET, consider the following suggestions in order:
 
-✔️ CONSIDER using the [.NET Upgrade Assistant](upgrade-assistant-overview.md) to migrate your projects. Even though this tool is in preview, it automates most of the manual steps detailed in this article and gives you a great starting point for continuing your migration path.
+✔️ CONSIDER using the [GitHub Copilot app modernization](github-copilot-app-modernization-overview.md) to migrate your projects. GitHub Copilot is powerful at identifying and fixing incompatibilities when porting. It automates most of the manual steps detailed in this article and gives you a great starting point for continuing your migration path.
 
 ✔️ CONSIDER examining your dependencies first. Your dependencies must target .NET, .NET Standard, or .NET Core.
 
@@ -208,16 +202,16 @@ When porting your application to .NET, consider the following suggestions in ord
 
 ✔️ CONSIDER targeting .NET 8, which is a long-term support (LTS) release.
 
-✔️ DO target .NET 6+ for **Windows Forms and WPF** projects. .NET 6 and later versions contain many improvements for Desktop apps.
+✔️ DO target .NET 8+ for **Windows Forms and WPF** projects. .NET 8 and later versions contain many improvements for Desktop apps.
 
 ✔️ CONSIDER targeting .NET Standard 2.0 if you're migrating a library that might also be used with .NET Framework projects. You can also multitarget your library, targeting both .NET Framework and .NET Standard.
 
 ✔️ DO add reference to the [Microsoft.Windows.Compatibility NuGet package](https://www.nuget.org/packages/Microsoft.Windows.Compatibility) if, after migrating, you get errors of missing APIs. A large portion of the .NET Framework API surface is available to .NET via the NuGet package.
 
 ## See also
 
-- [Overview of the .NET Upgrade Assistant](upgrade-assistant-overview.md)
+- [What is GitHub Copilot app modernization](github-copilot-app-modernization-overview.md)
 - [ASP.NET to ASP.NET Core migration](/aspnet/core/migration/proper-to-2x)
-- [How to upgrade a WPF desktop app to .NET](/dotnet/desktop/wpf/migration/)
-- [Migrate .NET Framework Windows Forms apps to .NET](/dotnet/desktop/winforms/migration/)
-- [.NET 5 vs. .NET Framework for server apps](../../standard/choosing-core-framework-server.md)
+- [Upgrade a WPF desktop app to .NET](/dotnet/desktop/wpf/migration/)
+- [Upgrade a Windows Forms app to .NET](/dotnet/desktop/winforms/migration/)
+- [.NET vs. .NET Framework for server apps](../../standard/choosing-core-framework-server.md)

docs/core/porting/github-copilot-app-modernization-faq.yml

@@ -10,7 +10,7 @@ metadata:
 
 title: GitHub Copilot app modernization FAQ
 summary: |
-  GitHub Copilot app modernization is an interactive GitHub Copilot agent that adds powerful upgrade capabilities to Visual Studio. This article answers frequently asked questions. For more information about the tool, see [What is GitHub Copilot app modernization?](github-copilot-app-modernization-overview.md).
+  GitHub Copilot app modernization is an interactive GitHub Copilot agent that adds powerful upgrade capabilities to Visual Studio. This article answers frequently asked questions. For more information about the tool, see [What is GitHub Copilot app modernization](github-copilot-app-modernization-overview.md).
 
   The tool requires one of the following GitHub Copilot subscriptions:
 
@@ -24,7 +24,7 @@ sections:
     questions:
       - question: What can the agent do?
         answer: |
-          Currently, GitHub Copilot app modernization helps you upgrade your .NET projects to newer versions of .NET. The agent is an extension for Visual Studio that performs the following steps in a GitHub Copilot chat session:
+          Currently, GitHub Copilot app modernization helps you upgrade your .NET (.NET, .NET Core, and .NET Framework) projects to newer versions of .NET. It also helps migrate services to Azure. It also upgrades dependencies and fixes errors in the code post-migration. The agent performs the following steps in a GitHub Copilot chat session:
 
           - Analyzes your projects and proposes an upgrade plan.
           - According to the plan, runs a series of tasks to upgrade your projects.
@@ -35,9 +35,7 @@ sections:
 
       - question: What can the agent upgrade?
         answer: |
-          GitHub Copilot app modernization currently focuses on migrating your projects from one version of .NET to another. For example, upgrading from .NET Core 3.1 or .NET 6, to .NET 9. It also upgrades dependencies and fixes errors in the code post-migration.
-
-          Besides upgrading the target framework, the agent can work with the following types of projects:
+          GitHub Copilot app modernization helps you upgrade your .NET projects or migrate them to Azure. Besides upgrading the target framework, the agent can work with the following types of projects:
 
           - Azure Functions.
           - Console apps and class libraries.
@@ -71,6 +69,10 @@ sections:
 
           However, the agent does have some adaptability within a session. If you manually adjust a fix, it learns from that interaction in the short term and applies similar corrections if it encounters the same issue again. Think of it as refining its approach within the scope of that upgrade. We never store a user's codebase and never use your code for training the model. Once an upgrade is complete, session data is deleted and not stored.
 
+      - question: Can I provide feedback?
+        answer: |
+          Yes! Use the [Suggest a feature](/visualstudio/ide/suggest-a-feature) and [Report a Problem](/visualstudio/ide/report-a-problem) features of in Visual Studio to provide feedback.
+
 additionalContent: |
     ## Related content
 

docs/core/porting/github-copilot-app-modernization-overview.md

@@ -20,17 +20,21 @@ This process streamlines modernization and boosts developer productivity and con
 With this assistant, you can:
 
 - Upgrade to a newer version of .NET.
-- Migrate technolgies to Azure.
+- Migrate technologies to Azure.
 - Modernize your .NET app, especially when upgrading from .NET Framework.
 - Assess your application's code, configuration, and dependencies.
 - Plan and set up the right Azure resource.
 - Fix issues and apply best practices for cloud migration.
 - Validate that your app builds and tests successfully.
 
+## Feedback
+
+Feedback is important to Microsoft and the efficiency of this agent. Use the [Suggest a feature](/visualstudio/ide/suggest-a-feature) and [Report a Problem](/visualstudio/ide/report-a-problem) features of in Visual Studio to provide feedback.
+
 ## Prerequisites
 
 - Windows Operating System
-- [Visual Studio 2022 version 17.14.16 or newer](https://visualstudio.microsoft.com/downloads/)—or—[Visual Studio 2026 Insiders Preview 2 or newer](https://visualstudio.microsoft.com/insiders)
+- [Visual Studio 2022 version 17.14.16 or newer](https://visualstudio.microsoft.com/downloads/) (To be released).
 - [.NET desktop development workload](/visualstudio/install/modify-visual-studio?view=vs-2022&preserve-view=true#change-workloads-or-individual-components) with the following optional components enabled:
 
   - GitHub Copilot
@@ -100,7 +104,7 @@ You can adjust the plan by editing the Markdown file to change the upgrade steps
 
 ### Perform the upgrade or migration
 
-Once an plan is ready, tell Copilot to start using it. Once the process starts, Copilot lets you know what it's doing in the chat window and it opens the **Upgrade Progress Details** document, which lists the status of every step.
+Once a plan is ready, tell Copilot to start using it. Once the process starts, Copilot lets you know what it's doing in the chat window and it opens the **Upgrade Progress Details** document, which lists the status of every step.
 
 If it runs into a problem, Copilot tries to identify the cause of a problem and apply a fix. If Copilot can't seem to correct the problem, it asks for your help. When you intervene, Copilot learns from the changes you make and tries to automatically apply them for you, if the problem is encountered again.
 

docs/core/porting/includes/github-copilot-suggestion.md

@@ -0,0 +1,2 @@
+> [!IMPORTANT]
+> Try the [GitHub Copilot app modernization chat agent](github-copilot-app-modernization-overview.md). This agent analyzes your projects and dependencies, produces a step-by-step migration plan with targeted recommendations and automated code fixes, and commits each change so you can validate or roll back. It automates common porting tasks—updating project files, replacing deprecated APIs, and resolving build issues—so you can modernize faster with less manual effort. For more information, see [What is GitHub Copilot app modernization](github-copilot-app-modernization-overview.md).

docs/core/porting/index.md

@@ -28,9 +28,9 @@ It also increases developer productivity by enabling newer SDKs, templates, and
 
 It's important to keep your developer tools up-to-date as each new release addresses security vulnerabilities and provides compatibility with new technologies.
 
-## Use GitHub Copilot Modernization agent
+## Use GitHub Copilot app modernization agent
 
-The GitHub Copilot Modernization agent provides an AI-assisted, end-to-end experience to speed porting and modernization work. The agent analyzes your project and writes a plan to complete your desired upgrade. You can adjust and iterate on the plan, then perform the upgrades. With this assistant, you can:
+The GitHub Copilot app modernization agent provides an AI-assisted, end-to-end experience to speed porting and modernization work. The agent analyzes your project and writes a plan to complete your desired upgrade. You can adjust and iterate on the plan, then perform the upgrades. With this assistant, you can:
 
 - Upgrade projects to a newer .NET version.
 - Assess your application's code, configuration, and dependencies.
@@ -40,4 +40,4 @@ The GitHub Copilot Modernization agent provides an AI-assisted, end-to-end exper
 - Fix issues and apply cloud-migration best practices.
 - Validate that your app builds and that tests pass.
 
-Use the GitHub Copilot Modernization agent when you want a guided, AI-powered path to assess, remediate, and modernize codebases—particularly for projects that have many dependencies, rely on Windows-specific APIs, or when you plan to containerize or migrate services to the cloud.
+Use the GitHub Copilot app modernization agent when you want a guided, AI-powered path to assess, remediate, and modernize codebases—particularly for projects that have many dependencies, rely on Windows-specific APIs, or when you plan to containerize or migrate services to the cloud.

docs/core/porting/modernize.md

@@ -10,10 +10,7 @@ ms.custom: sfi-ropc-nochange
 
 # Modernize after upgrading to .NET from .NET Framework
 
-In this article, you'll learn about different ways you can modernize your app after it's been upgraded from .NET Framework to .NET. Use the [.NET Upgrade Assistant](upgrade-assistant-overview.md) tool to upgrade your app to .NET.
-
-> [!TIP]
-> You can use GitHub Copilot to modernize your application after migrating from .NET Framework. For more information, see [What is GitHub Copilot app modernization?](github-copilot-app-modernization-overview.md).
+In this article, you'll learn about different ways you can modernize your app after it's been upgraded from .NET Framework to .NET. Use the [GitHub Copilot app modernization](github-copilot-app-modernization-overview.md) assistant to upgrade your app to .NET.
 
 ## Missing APIs
 
@@ -29,7 +26,7 @@ Projects that target a Windows desktop technology, such as Windows Presentation
 
 ## App.config
 
-.NET Framework uses the _App.config_ file to load settings for your app, such as connection strings and log provider configuration. Modern .NET uses the _appsettings.json_ file for app settings. The CLI version of the Upgrade Assistant handles converting _App.config_ files to _appsettings.json_, but the Visual Studio extension doesn't.
+.NET Framework uses the _App.config_ file to load settings for your app, such as connection strings and log provider configuration. Modern .NET uses the _appsettings.json_ file for app settings.
 
 > [!TIP]
 > If you don't want to use the _appsettings.json_ file, you can add the `System.Configuration.ConfigurationManager` NuGet package to your app and your code will compile and use the _App.config_ file.

docs/core/porting/porting-approaches.md

@@ -3,20 +3,20 @@ title: Porting approaches
 description: Create a porting plan that best reflects your project and context.
 author: StephenBonikowsky
 ms.author: stebon
-ms.date: 06/10/2021
+ms.date: 09/15/2025
 ---
 # Create a porting plan
 
-We recommend using the Visual Studio [.NET Upgrade Assistant](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant) to update .NET Framework code to the latest .NET versions. For more information see the blog [Upgrading your .NET projects with Visual Studio](https://devblogs.microsoft.com/dotnet/upgrade-assistant-now-in-visual-studio/).
-
-[!INCLUDE[](~/includes/deprecating-api-port.md)]
-
 Before you jump straight into the code, take the time to go through the recommended pre-migration steps. This article gives you insight into the kinds of issues you may come across, and helps you decide on an approach that makes the most sense.
 
+[!INCLUDE[](../../../includes/deprecating-api-port.md)]
+
 ## Port your code
 
 Make sure that you follow the [prerequisites to porting code](premigration-needed-changes.md) before you continue any further. Be ready to decide on the best approach for you and begin porting code.
 
+[!INCLUDE [github-copilot-suggestion](includes/github-copilot-suggestion.md)]
+
 ### Deal primarily with the compiler
 
 This approach works well for small projects or projects that don't use many .NET Framework APIs. The approach is simple:
@@ -98,5 +98,5 @@ If you start with the base of your library and move outward from the base and te
 
 ## Next steps
 
-- [Overview of the .NET Upgrade Assistant](upgrade-assistant-overview.md)
+- [What is GitHub Copilot app modernization](github-copilot-app-modernization-overview.md)
 - [Organize your project to support both .NET Framework and .NET Core](project-structure.md)

docs/core/porting/premigration-needed-changes.md

@@ -9,6 +9,8 @@ ms.date: 06/10/2021
 
 Make the needed changes to build and run a .NET application before beginning the work to port your code. These changes can be done while still building and running a .NET Framework application.
 
+[!INCLUDE [github-copilot-suggestion](includes/github-copilot-suggestion.md)]
+
 ## Upgrade to required tooling
 
 Upgrade to a version of MSBuild/Visual Studio that supports the version of .NET you will be targeting. See [Versioning relationship between the .NET SDK, MSBuild and VS](versioning-sdk-msbuild-vs.md) for more info.