Update GitHub Copilot upgrade scenarios and skills reference - #55438
Merged
Conversation
Refreshes the reference against microsoft/upgrade-agent-plugins (root agent plus the upgrade-dotnet extender): 15 scenarios and 78 upgrade skills. Scenarios: adds Azure migration, ARM64 migration, .NET Framework 4.8.1 version upgrade, NuGet package upgrade, VSSDK SDK-style conversion, and WinForms feature adoption. Reworks the Web Forms scenario to target Blazor Server. Skills: adds new desktop (WinForms) and testing tables, five common skills, YARP proxy scaffolding, two Blazor Server skills, and three library skills. Regroups the OWIN and Azure library skills to match the upstream folder layout and drops the nonexistent generic Azure SDK skill. Fixes #55319 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Copilot upgrade for .NET scenarios-and-skills reference to match the current upstream set of supported scenarios and upgrade skills, including new scenarios and expanded skill groupings.
Changes:
- Expanded the scenarios list from 9 to 15, adding new upgrade/migration workflows and updating the Web Forms scenario to specify Blazor Server.
- Reworked and regrouped the skills reference to reflect upstream organization and to expand skill descriptions with concrete APIs and behaviors.
- Added new skill categories (desktop and testing) and clarified how/when certain library skills activate.
Suppressed comments (1)
docs/core/porting/github-copilot-upgrade/scenarios-and-skills.md:150
- This row calls out
Form.ShowAsync/Form.ShowDialogAsync, but it doesn't mention that these WinForms APIs are experimental in .NET 9 and require opting in (warningWFO5002). Adding that note makes the skill description actionable and avoids surprise build errors.
| **Managing WinForms async APIs** | Adopts `Control.InvokeAsync`, `Form.ShowAsync`, `Form.ShowDialogAsync`, and `TaskDialog.ShowDialogAsync` in place of `Control.Invoke` and `BeginInvoke`. |
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.
Fixes #55319
Refreshes the scenarios and skills reference against the upstream source of truth,
microsoft/upgrade-agent-plugins— specifically the root agent and theupgrade-dotnetextender.The article previously listed 9 scenarios and ~55 skills. Upstream now ships 15 scenarios and 78 upgrade skills.
Scenarios
Six new scenarios:
azure-migratedotnet-arm64-migrationdotnet-framework-version-upgradenuget-package-upgradevssdk-sdk-style-conversionwinforms-feature-adoptionThe Web Forms scenario was reworked — upstream is now
webforms-to-blazor-server, so the article says Blazor Server rather than generic Blazor. The .NET version upgrade section also notes the post-completion suggestions (Aspire, EF6→EF Core, WinForms features, ARM64) and report generation.Skills
desktop/winformsskills: Designer code, custom controls, async APIs, data binding, high-DPI layout, MVVM, rendering, and app structure.generating-upgrade-test-baselineandmanaging-dotnet-test-installation.building-projects,managing-target-frameworks,managing-package-references,managing-legacy-dotnet-packages,modifying-project-properties.scaffolding-yarp-proxy-project, plus the two Blazor Server skills (authentication, data access) in a new "Web Forms and Blazor Server" subsection.migrating-cosmosdb-bulk-executor,migrating-documentdb-to-cosmos,migrating-razorengine-to-razorlight.Regrouping and corrections
libraries/upstream, not under web/cloud. Tables now mirror the upstream folder layout.SKILL.mdfrontmatter.Content source
Every scenario and skill row was taken from the
descriptionfrontmatter of the corresponding upstreamSKILL.mdfile, then condensed into the article's existing prose style. No skill descriptions were invented.Scope decisions
Validation
SKILL.mdfiles underlazy/, 78 skill rows in the article.###headings in the page.markdownlint-cli2passes with 0 issues.ai-usage: ai-assistedis retained in the frontmatter, andms.dateis bumped.Internal previews