You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/core/porting/github-copilot-app-modernization/overview.md
+29-19Lines changed: 29 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,16 @@ titleSuffix: ""
5
5
author: adegeo
6
6
ms.author: adegeo
7
7
ms.topic: overview
8
-
ms.date: 09/23/2025
8
+
ms.date: 12/09/2025
9
+
ai-usage: ai-assisted
9
10
10
-
#customer intent: As a developer, I want to learn about what the GitHub Copilot app modernziation is, so that I understand its capabilities and how I can take advantage of it.
11
+
#customer intent: As a developer, I want to learn about what the GitHub Copilot app modernization is, so that I understand its capabilities and how I can take advantage of it.
11
12
12
13
---
13
14
14
15
# What is GitHub Copilot app modernization?
15
16
16
-
GitHub Copilot app modernization is a GitHub Copilot agent that helps upgrade projects to newer versions of .NET and migrate .NET applications to Azure quickly and confidently by guiding you through assessment, solution recommendations, code fixes, and validation - all within Visual Studio.
17
+
GitHub Copilot app modernization is a GitHub Copilot agent that helps you upgrade projects to newer versions of .NET and migrate .NET applications to Azure quickly and confidently. It guides you through assessment, solution recommendations, code fixes, and validation—all within Visual Studio.
17
18
18
19
This process streamlines modernization and boosts developer productivity and confidence. GitHub Copilot app modernization is an all-in-one upgrade and migration agent that uses AI to improve developer velocity, quality, and results.
19
20
@@ -33,19 +34,21 @@ Feedback is important to Microsoft and the efficiency of this agent. Use the [Su
33
34
34
35
## Prerequisites
35
36
36
-
The following items are required before you can use GitHub Copilot app modernization:
37
+
Before using GitHub Copilot app modernization, you need these items:
If your repository already contains the `.github/upgrades` folder with the stage files from a previous upgrade or migration attempt, Copilot asks whether you want to continue that upgrade or start over with a fresh analysis.
48
+
46
49
## Upgrade .NET projects
47
50
48
-
The modernization agent supports upgrading projects coded in C#. The following types of projects are supported:
51
+
The modernization agent supports upgrading projects coded in C#. The agent supports the following project types:
49
52
50
53
- ASP.NET Core (and related technologies such as MVC, Razor Pages, and Web API)
51
54
- Blazor
@@ -59,7 +62,7 @@ To learn how to start an upgrade, see [How to upgrade a .NET app with GitHub Cop
59
62
60
63
### Upgrade paths
61
64
62
-
The following upgrade paths are supported:
65
+
The agent supports the following upgrade paths:
63
66
64
67
- Upgrade projects from older .NET versions to the latest.
65
68
- Upgrade .NET Framework projects to .NET.
@@ -68,7 +71,7 @@ The following upgrade paths are supported:
68
71
69
72
## Migrate .NET projects to Azure
70
73
71
-
The modernization agent combines automated analysis, AI-driven code remediation, build and vulnerability checks, and deployment automation to simplify migrations to Azure. The following capabilities describe how the agent assesses readiness, applies fixes, and streamlines the migration process:
74
+
The modernization agent combines automated analysis, AI-driven code remediation, build and vulnerability checks, and deployment automation to simplify migrations to Azure. The agent assesses readiness, applies fixes, and streamlines the migration process through these capabilities:
Automatically builds your app and resolves compilation errors and vulnerabilities, streamlining development.
86
+
Automatically build your app and resolve compilation errors and vulnerabilities, streamlining development.
84
87
85
88
- Seamless Deployment.
86
89
@@ -129,29 +132,36 @@ Predefined tasks capture industry best practices for using Azure services. Curre
129
132
-**Migrate to Azure Cache for Redis with Managed Identity**
130
133
Replace in-memory or local Redis cache implementations with Azure Cache for Redis for high availability, scalability, and enterprise-grade security.
131
134
132
-
## How does it work
135
+
## How it works
133
136
134
-
Once you request the modernization agent to upgrade or migrate your app, Copilot analyzes your projects and their dependencies, and then asks you a series of questions about the upgrade or migration. After you answer these questions, a plan is written in the form of a Markdown file. If you tell Copilot to proceed with the upgrade or migration, it follows the steps described in the plan.
137
+
When you ask the modernization agent to upgrade or migrate your app, Copilot first prompts you to create a new branch if you're working in a Git repository. Then Copilot runs a three-stage workflow. Each stage writes a Markdown file under `.github/upgrades`in your repository so you can review what comes next before you continue. If `.github/upgrades` already exists from a prior attempt, Copilot asks whether to continue or start fresh.
135
138
136
-
You can adjust the plan by editing the Markdown file to change the upgrade steps or add more context.
139
+
-**Analysis stage (`assessment.md`)**\
140
+
Copilot examines your project structure, dependencies, and code patterns to build a comprehensive assessment. The document lists breaking changes, API compatibility issues, deprecated patterns, and the migration scope so you know exactly what needs attention.
137
141
138
-
### Perform the upgrade or migration
142
+
-**Planning stage (`plan.md`)**\
143
+
Copilot converts the assessment into a detailed specification that explains how to resolve every issue. The plan documents migration strategies, refactoring approaches, dependency upgrade paths, and risk mitigations.
144
+
145
+
-**Execution stage (`tasks.md`)**\
146
+
Copilot breaks the plan into sequential, concrete tasks with validation criteria. Each task describes a single change and how Copilot confirms it succeeded.
139
147
140
-
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.
148
+
Edit any of the Markdown files in `.github/upgrades` to adjust upgrade steps or add context before you move forward.
149
+
150
+
### Perform the upgrade or migration
141
151
142
-
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.
152
+
As each stage is prepared, tell Copilot to move on to the next stage, giving you time to research and modify (if necessary) any of the tasks the stage has laid out.
143
153
144
-
Each major step in the plan is committed to the local Git repository.
154
+
Once you reach the last stage, **Execution stage**, tell Copilot to start the upgrade or migration. If Copilot runs into a problem, it tries to identify the cause and apply a fix. If Copilot can't 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.
145
155
146
156
### Upgrade and migration results
147
157
148
-
When the process completes, a report is generated that describes every step taken by Copilot. The tool creates a Git commit for every portion of the process, so you can easily roll back the changes or get detailed information about what changed. The report contains the Git commit hashes.
158
+
As Copilot runs each task, it updates the `tasks.md` file in `.github/upgrades` with the status of every step. Monitor progress by reviewing this file. The tool creates a Git commit for every portion of the process, so you can easily roll back the changes or get detailed information about what changed.
149
159
150
-
The report also provides a _Next steps_ section that describes the steps you should take after the upgrade finishes.
160
+
When the upgrade or migration finishes, Copilot displays next steps in the chat response to guide you on what to do after the process completes.
151
161
152
162
## Telemetry
153
163
154
-
The tool only collects data about project types, intent to upgrade, and upgrade duration. The data is collected and aggregated through Visual Studio itself and doesn't contain any user-identifiable information. For more information about Microsoft's privacy policy, see [Visual Studio Customer Experience Improvement Program](/visualstudio/ide/visual-studio-experience-improvement-program?view=visualstudio&preserve-view=true).
164
+
The tool collects data about project types, intent to upgrade, and upgrade duration. Visual Studio itself collects and aggregates the data and doesn't contain any user-identifiable information. For more information about Microsoft's privacy policy, see [Visual Studio Customer Experience Improvement Program](/visualstudio/ide/visual-studio-experience-improvement-program?view=visualstudio&preserve-view=true).
0 commit comments