dotnet-upgrade Skill
Transformation rules and verification steps for upgrading .NET Framework 4.x applications to .NET 9. WHEN: upgrade to .NET 9, migrate .NET Framework, retarget TFM, convert to SDK-style project, System.Web replacement, web.config migration, packages.config to PackageReference, binding redirect cleanup. NOT for: greenfie Published by microsoft in MicroHack.
What is dotnet-upgrade Skill?
Transformation rules and verification steps for upgrading .NET Framework 4.x applications to .NET 9. WHEN: upgrade to .NET 9, migrate .NET Framework, retarget TFM, convert to SDK-style project, System.Web replacement, web.config migration, packages.config to PackageReference, binding redirect cleanup. NOT for: greenfie Published by microsoft in MicroHack. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using MicroHack
Technical details
- Install or run with Copy skill directory
When to use dotnet-upgrade Skill
- Use it for developers using microhack.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/MicroHack
- Skill file: 03-Azure/01-01-App Innovation/03_GHCPAppModernization/templates/skills/dotnet-upgrade/SKILL.md
What it does
Transformation rules and verification steps for upgrading .NET Framework 4.x applications to .NET 9. WHEN: upgrade to .NET 9, migrate .NET Framework, retarget TFM, convert to SDK-style project, System.Web replacement, web.config migration, packages.config to PackageReference, binding redirect cleanup. NOT for: greenfie
Skill instructions
.NET Framework 4.x → .NET 9 Upgrade Rules Purpose Packages the API mappings, project-file rules, and verification checklist needed to retarget a .NET Framework app to .NET 9 without behavioral change. Prerequisites - ASSESSMENT.md exists and is approved (AppCAT findings available). - .NET 9 SDK installed — verify: dotnet --list-sdks. Procedure Step 1 — Convert to SDK-style projects (leaf projects first) powershell dotnet tool install -g upgrade-assistant upgrade-assistant upgrade .\src{{Project}}.csproj - Migrate packages.config → PackageReference. - Delete AssemblyInfo.cs attributes now generated by the SDK. - Remove binding redirects from app/web.config (not honored on .NET 9). Step 2 — Apply API transformation rules | Source pattern (.NET Framework) | Target pattern (.NET 9) | Notes | |---|---|---| | System.Web.Mvc controllers | Microsoft.AspNetCore.Mvc | Routing moves to endpoint routing | | Global.asax / HttpModule | ASP.NET Core middleware in Program.cs | Order matters — replica
Explore related resources
Frequently asked questions
What is dotnet-upgrade?
dotnet-upgrade is a open-source AI agent skill with Copy skill directory. Transformation rules and verification steps for upgrading .NET Framework 4.x applications to .NET 9.
Who is dotnet-upgrade best for?
dotnet-upgrade is best for reusing agent instructions, scripts, and references.
How do I install dotnet-upgrade?
Install or run dotnet-upgrade using Copy skill directory. Check dotnet-upgrade for the latest setup command.
Is dotnet-upgrade actively maintained?
dotnet-upgrade may need a closer maintenance check before production use.
Auto-fetched from GitHub.
