-
Notifications
You must be signed in to change notification settings - Fork 6.1k
[Draft] Add docs for dotnet migration support for copilot cli #49730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 2 commits
43a659c
83029c4
b5fb4fe
7bc4367
c583ca0
2a95d37
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,88 @@ | ||||||
| --- | ||||||
| title: Migrate .NET Apps to Azure Using GitHub Copilot App Modernization in Copilot CLI | ||||||
| description: Provides an overview of how .NET developers can migrate applications to Azure using GitHub Copilot App Modernization in the Copilot CLI. | ||||||
| ms.topic: concept-article | ||||||
| ms.custom: devx-track-dotnet | ||||||
| ms.date: 11/11/2025 | ||||||
| author: alexwolfmsft | ||||||
| ms.author: alexwolf | ||||||
| ms.reviewer: jessiehuang | ||||||
| --- | ||||||
|
|
||||||
| # Migrate .NET Apps to Azure Using GitHub Copilot App Modernization in Copilot CLI | ||||||
|
|
||||||
| ## Overview | ||||||
|
|
||||||
| This article provides an overview of how .NET developers can migrate their applications to Azure using **GitHub Copilot App Modernization** within the [**Copilot CLI**](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/use-copilot-cli), enabling them to modernize applications wherever they code. It’s currently in public preview — give it a try and let us know if any [feedback](https://aka.ms/ghcp-appmod/feedback). | ||||||
| :::image type="content" source="./media/copilot-cli-entrance.png" lightbox="./media/copilot-cli-entrance.png" alt-text="Screenshot of app mod entrance in Copilot CLI"::: | ||||||
|
|
||||||
| >[!NOTE] | ||||||
| >GitHub Copilot CLI is available with the GitHub Copilot Pro, GitHub Copilot Pro+, GitHub Copilot Business and GitHub Copilot Enterprise plans. | ||||||
| >If you receive Copilot from an organization, the Copilot CLI policy must be enabled in the organization's settings. | ||||||
|
|
||||||
| ## Why Use Copilot CLI with App Modernization | ||||||
| - Run modernization tasks directly from the terminal — no need to switch to an IDE | ||||||
| - Supports both interactive (human-in-the-loop) and batch workflows | ||||||
|
Comment on lines
+23
to
+25
|
||||||
|
|
||||||
| ## Prerequisites | ||||||
| - [Install Copilot CLI](https://docs.github.com/en/copilot/how-tos/set-up/install-copilot-cli) | ||||||
| - A GitHub Copilot subscription, See [Copilot plans](https://github.com/features/copilot/plans?ref_product=copilot) | ||||||
|
||||||
| - Node.js version 22 or later | ||||||
| - npm version 10 or later | ||||||
|
|
||||||
| ## Getting Started | ||||||
| 1. In your terminal, navigate to the .NET project folder containing the code you want to work on. | ||||||
| 2. Enter `copilot` to start Copilot CLI. | ||||||
| ``` | ||||||
| copilot | ||||||
| ``` | ||||||
| Copilot will ask you to confirm that you trust the files in this folder. Refer to [Using Copilot CLI](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/use-copilot-cli#trusted-directories) | ||||||
|
||||||
| Choose one of the options: | ||||||
|
Comment on lines
+38
to
+39
|
||||||
| - Yes, proceed: Copilot can work with the files in this location for this session only. | ||||||
| - Yes, and remember this folder for future sessions: You trust the files in this folder for this and future sessions. You won't be asked again when you start Copilot CLI from this folder. Only choose this option if you are sure that it will always be safe for Copilot to work with files in this location. | ||||||
|
||||||
| - No, exit (Esc): End your Copilot CLI session. | ||||||
|
Comment on lines
+40
to
+42
|
||||||
| 3. You can add MCP servers by running `/mcp add` in Copilot CLI according to the configuration below, here is an example of adding .NET migration MCP: | ||||||
|
||||||
| ``` | ||||||
| /mcp add net-migrate | ||||||
| ``` | ||||||
| Or by manually updating the `~/.config/mcp-config.json` file with the following info. Refer to [Add an MCP server](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/use-copilot-cli#add-an-mcp-server) | ||||||
|
||||||
| ``` | ||||||
| { | ||||||
| "mcpServers": { | ||||||
| "dotnet-migrate": { | ||||||
| "type": "local", | ||||||
| "tools": [ | ||||||
| "*" | ||||||
| ], | ||||||
| "command": "npx", | ||||||
| "args": [ | ||||||
| "-y", | ||||||
| "net-migrate" // TODO: update to actual package name | ||||||
|
||||||
| "net-migrate" // TODO: update to actual package name | |
| "net-migrate" |
Copilot
AI
Nov 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The phrase "You can run" is weak. Per the Markdown style guidelines, use imperative mood for instructions. Change to "Run /mcp show to verify the MCP servers are correctly configured."
Copilot
AI
Nov 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing period at end of the numbered list item heading. Per the Markdown style guidelines, list items with more than three words must end with periods.
Copilot
AI
Nov 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing period at end of sentence after the link. Add a period after the closing parenthesis.
Outdated
Copilot
AI
Nov 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing blank line between the paragraph and the code block that follows. Per the Markdown style guidelines, add blank lines around Markdown elements.
Copilot
AI
Nov 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grammatical error. The phrase "will be executed and showing" mixes future tense with present participle incorrectly. Change to "Then the migration task is executed and shows progress in Copilot CLI" or "The migration task executes and shows progress in Copilot CLI."
Copilot
AI
Nov 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing period at end of the sentence. Per the Markdown style guidelines, add a period at the end.
Outdated
Copilot
AI
Nov 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awkward phrasing. Change "with below summary" to "with the following summary" for clarity and proper grammar.
Copilot
AI
Nov 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
List items should not end with periods when they are single links or fewer than three words. However, this contains more than three words as the link text, so the period is appropriate. The issue is the period should be outside the link, not as part of the markdown. Move the period outside the closing parenthesis to after it (already correct in the code). Actually reviewing more carefully, the period is already correctly placed outside. No change needed. However, for list items that are just links, the guideline is that list items with more than three words need periods. Since this is a single reference link, consider if this should have a period - reviewing the guidelines, yes it should since it's more than three words.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The phrase "give it a try and let us know if any [feedback]" uses passive construction. Per the Markdown style guidelines, use active voice and imperative mood. Rephrase to "Try it out and share your [feedback]" or "Try it and let us know your [feedback]".