Rewrite migration articles for App Modernization Agent#2247
Open
adegeo wants to merge 16 commits into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR modernizes the WinForms and WPF migration documentation by replacing the retired Upgrade Assistant–based walkthroughs with GitHub Copilot modernization agent guidance, and by introducing a shared migration include used by both stacks.
Changes:
- Rewrites WinForms and WPF migration landing pages as upgrade-path overviews that include shared migration guidance.
- Adds new step-by-step WinForms and WPF upgrade tutorials using the GitHub Copilot modernization agent.
- Updates the WinForms TOC to surface the new overview and tutorial.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| dotnet-desktop-guide/wpf/migration/index.md | Replaces the prior how-to content with an overview page and shared migration include. |
| dotnet-desktop-guide/wpf/migration/how-to-upgrade-wpf.md | Adds a new WPF modernization-agent upgrade walkthrough. |
| dotnet-desktop-guide/winforms/toc.yml | Updates WinForms navigation to point to the new overview and upgrade tutorial. |
| dotnet-desktop-guide/winforms/migration/index.md | Replaces the prior how-to content with an overview page and shared migration include. |
| dotnet-desktop-guide/winforms/migration/how-to-upgrade-winforms.md | Adds a new WinForms modernization-agent upgrade walkthrough. |
| dotnet-desktop-guide/includes/migration-shared.md | Introduces shared migration/upgrade guidance consumed by both WinForms and WPF migration overviews. |
Comment on lines
+4
to
+8
| author: adegeo | ||
| ms.author: adegeo | ||
| ms.topic: overview | ||
| ms.date: 06/11/2026 | ||
| ai-usage: ai-assisted |
Comment on lines
+4
to
+8
| author: adegeo | ||
| ms.author: adegeo | ||
| ms.topic: overview | ||
| ms.date: 06/11/2026 | ||
| ai-usage: ai-assisted |
|
|
||
| Staying current on .NET versions matters too. Each .NET release has a defined support window, and apps running on an out-of-support version stop receiving security patches and fixes. Upgrade before end-of-support to stay protected. | ||
|
|
||
| .NET offers meaningful performance improvements across runtime startup, throughput, and memory usage. Desktop apps on .NET also benefits from ongoing feature investment—newer controls, accessibility improvements, high-DPI enhancements, and better integration with Windows such as Dark Mode on Windows 11 are shipped in .NET only. You also gain access to newer C# and Visual Basic language features, improved tooling, and a rich ecosystem of NuGet packages that target .NET. |
Comment on lines
+125
to
+127
| > | Windows Forms | 621 | 76.0% | Windows Forms APIs for building Windows desktop applications with traditional Forms-based UI that are available in .NET on Windows. Enable Windows Desktop support: Option 1 (Recommended): Target net9.0-windows; Option 2: Add `<UseWindowsDesktop>true</UseWindowsDesktop>`; Option 3 (Legacy): Use Microsoft.NET.Sdk.WindowsDesktop SDK. | | ||
|
|
||
| Most of these issues aren't real problems. Look at the "Migration Path" column for the _GDI+_ row that lists 208 issues. The assessment flags these APIs because they're available in .NET Framework but not in .NET. The column explains the fix: add the `System.Drawing.Common` NuGet package to restore the APIs. The _Windows Forms_ row lists 621 API issues for the same reason. Windows Forms APIs aren't available in .NET by default, but you restore them through the project option `<UseWindowsDesktop>` and by targeting a Windows-specific framework like `net10.0-windows`. |
Comment on lines
+189
to
+190
| <OutputType>Library</OutputType> | ||
| <MyType>Windows</MyType> |
| <PropertyGroup> | ||
| <TargetFramework>net10.0-windows</TargetFramework> | ||
| <UseWPF>true</UseWPF> | ||
| <OutputType>Library</OutputType> |
| - **Flow Mode**: Defaults to **Automatic**. For complex apps, ask the agent to switch to **Guided** mode. | ||
| - **Source Control**: Indicates that the agent creates a new working branch. | ||
|
|
||
| The agent writes its work to `.github/upgrades/dotnet-version-upgrade/` in your repository. If that folder already exists from a prior attempt, the agent asks whether to continue or start fresh. |
| - **Flow Mode**: Defaults to **Automatic**. For complex apps, ask the agent to switch to **Guided** mode. | ||
| - **Source Control**: Indicates that the agent creates a new working branch. | ||
|
|
||
| The agent writes its work to `.github/upgrades/dotnet-version-upgrade/` in your repository. If that folder already exists from a prior attempt, the agent asks whether to continue or start fresh. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TODO:
Fixes #2165
Internal previews