dotnet-upgrade

Automate in-place .NET project upgrades to the latest stable LTS version.

Updated Mar 6, 2026

Search Tags:#automation #ci/cd #migration #upgrade #nuget #.net

Ready to run

npx skills add https://github.com/sarjangi/Copilot-Customer --skill dotnet-upgrade-sarjangi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-upgrade
Source: https://github.com/sarjangi/Copilot-Customer/tree/main/.github/dotnet/skills/dotnet-upgrade
Command: npx skills add https://github.com/sarjangi/Copilot-Customer --skill dotnet-upgrade-sarjangi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of upgrading .NET projects to the latest stable LTS version, minimizing manual intervention and potential errors.

Core Features & Use Cases

Full In-Place Upgrades: Handles TargetFramework updates, NuGet package management, and build/test validation.
Automated Fixes: Resolves upgrade-related warnings and minor build errors automatically.
CI/CD Suggestions: Identifies necessary changes for pipelines and presents them for human review.
Use Case: Upgrade an entire .NET solution from .NET 6 to .NET 8, including all projects and dependencies, with a single command.

Quick Start

Use the dotnet-upgrade skill to upgrade all projects in the repository to .NET 8.

Frequently Asked Questions about dotnet-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate a .NET project upgrade to the latest LTS version?▼

Automating a .NET project upgrade requires updating the TargetFramework, managing NuGet packages, and validating builds. This Skill handles dependency ordering, breaking change analysis, and automatically resolves upgrade-related warnings and minor build errors in-place.

Can I upgrade an entire .NET solution and its NuGet dependencies with a single command?▼

Yes, you can upgrade an entire .NET solution, including all projects and NuGet dependencies, to the latest stable LTS version. The process handles dependency ordering and stops only on catastrophic build failures, ensuring a validated upgrade.

What happens to my CI/CD pipelines when migrating a .NET project to a new framework?▼

When migrating a .NET project, CI/CD pipeline adjustments are often necessary. This Skill identifies required pipeline changes and presents them for human review, ensuring your continuous integration process aligns with the new framework version.

Does the .NET upgrade process automatically fix build errors and warnings?▼

The .NET upgrade process automatically resolves minor build errors and warnings caused by the framework migration. It performs build and test validation, stopping the automated upgrade only when encountering catastrophic build failures that require manual intervention.

When should I not use automated migration for upgrading my .NET projects?▼

You should avoid automated migration for .NET projects when anticipating catastrophic build failures or complex breaking changes that require manual architectural intervention. The automation stops at critical failures, but highly customized solutions may need manual dependency resolution.