diff --git a/docs/core/porting/github-copilot-app-modernization-faq.yml b/docs/core/porting/github-copilot-app-modernization-faq.yml index 789c58e9bda7d..e88e28d7bb2f2 100644 --- a/docs/core/porting/github-copilot-app-modernization-faq.yml +++ b/docs/core/porting/github-copilot-app-modernization-faq.yml @@ -12,6 +12,13 @@ title: GitHub Copilot app modernization - upgrade for .NET FAQ summary: | GitHub Copilot app modernization - upgrade for .NET is an interactive GitHub Copilot extension 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 - upgrade for .NET?](github-copilot-app-modernization-overview.md). + The tool requires one of the following GitHub Copilot subscriptions: + + - Copilot Pro + - Copilot Pro+ + - Copilot Business + - Copilot Enterprise + sections: - name: Scenarios questions: diff --git a/docs/core/porting/github-copilot-app-modernization-install.md b/docs/core/porting/github-copilot-app-modernization-install.md index d659343c260ae..217b0bedbfe54 100644 --- a/docs/core/porting/github-copilot-app-modernization-install.md +++ b/docs/core/porting/github-copilot-app-modernization-install.md @@ -21,6 +21,17 @@ This article guides you through installing GitHub Copilot app modernization - up - [Visual Studio 2022 version 17.14 or newer](https://visualstudio.microsoft.com/downloads/) - [.NET desktop development workload](/visualstudio/install/modify-visual-studio?view=vs-2022&preserve-view=true#change-workloads-or-individual-components) +While not required to _install_ the extension, to use the extension you must [sign in to Visual Studio using a GitHub account](/visualstudio/ide/work-with-github-accounts) with [Copilot access](https://docs.github.com/copilot/about-github-copilot/what-is-github-copilot#getting-access-to-copilot). + +Supported GitHub Copilot subscription plans are: + +- Copilot Pro +- Copilot Pro+ +- Copilot Business +- Copilot Enterprise + +(If you change subscriptions, you must restart Visual Studio.) + ## Visual Studio extension The following steps install the Visual Studio extension. diff --git a/docs/core/porting/github-copilot-app-modernization-overview.md b/docs/core/porting/github-copilot-app-modernization-overview.md index fb435de6a4e90..52c8417ed5580 100644 --- a/docs/core/porting/github-copilot-app-modernization-overview.md +++ b/docs/core/porting/github-copilot-app-modernization-overview.md @@ -23,7 +23,16 @@ GitHub Copilot app modernization is distributed as a Visual Studio extension, an - [Visual Studio 2022 version 17.14 or newer](https://visualstudio.microsoft.com/downloads/). - [.NET desktop development workload](/visualstudio/install/modify-visual-studio?view=vs-2022&preserve-view=true#change-workloads-or-individual-components). - [Sign in to Visual Studio using a GitHub account](/visualstudio/ide/work-with-github-accounts) with [Copilot access](https://docs.github.com/copilot/about-github-copilot/what-is-github-copilot#getting-access-to-copilot). - - You can use [GitHub Copilot for free](/visualstudio/ide/copilot-free-plan). + + Supported subscription plans: + + - Copilot Pro + - Copilot Pro+ + - Copilot Business + - Copilot Enterprise + +(If you change subscriptions, you must restart Visual Studio.) + - Code must be in a local Git repository. - Code must be written in C#. - Optional but recommended: Use **GitHub Copilot agent mode** for the upgrade process. For more information, see [Use Copilot agent mode in Visual Studio](/visualstudio/ide/copilot-agent-mode?view=vs-2022&preserve-view=true). diff --git a/docs/core/porting/index.md b/docs/core/porting/index.md index cd3e21a48e705..3ab2af03991a0 100644 --- a/docs/core/porting/index.md +++ b/docs/core/porting/index.md @@ -1,8 +1,8 @@ --- -title: Port from .NET Framework to .NET 7 -description: Understand the porting process and discover tools you might find helpful when porting a .NET Framework project to .NET 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: 07/23/2024 +ms.date: 06/03/2025 ms.custom: devdivchpfy22, updateeachrelease no-loc: ["package.config", PackageReference] --- diff --git a/docs/core/porting/modernize.md b/docs/core/porting/modernize.md index 3620ca5f06f03..1cc827db32346 100644 --- a/docs/core/porting/modernize.md +++ b/docs/core/porting/modernize.md @@ -11,6 +11,9 @@ no-loc: ["package.config", PackageReference] 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 - upgrade for .NET?](github-copilot-app-modernization-overview.md). + ## Missing APIs When upgrading a .NET Framework app, you'll most likely have some incompatibilities. This is because .NET Framework is a Windows-only technology and .NET is a cross-platform technology. Some libraries aren't. For example, .NET doesn't provide out-of-the-box APIs to access the Windows Registry like .NET Framework did. Support for the Windows Registry is provided by the `Microsoft.Win32.Registry` NuGet package. Many .NET Framework-specific libraries have been ported to .NET or .NET Standard, and are hosted on NuGet. If you find a missing reference in your project, search NuGet.