dotnet-upgrade

Provides structured prompts for analyzing and executing .NET framework upgrades.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/lettucebo/Skills --skill dotnet-upgrade-lettucebo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-upgrade
Source: https://github.com/lettucebo/Skills/tree/main/skills/dotnet/dotnet-upgrade
Command: npx skills add https://github.com/lettucebo/Skills --skill dotnet-upgrade-lettucebo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Upgrading .NET solutions across multiple projects involves dependency conflicts, breaking API changes, pipeline updates, and validation work that is easy to miss without a systematic plan. ## Core Features & Use Cases - Assessment & Planning: Classify projects by framework type, detect legacy packages.config usage, and sequence upgrades from least to most dependent components. - Dependency & Code Modernization: Analyze NuGet package compatibility, transitive dependency conflicts, and deprecated API patterns such as WebHostBuilder to HostBuilder migrations. - CI/CD & Validation: Update Azure DevOps pipeline tasks like UseDotNet@2, define build and test validation strategies, and plan branching, PR, and release documentation workflows. - Use Case: A team migrating a large solution from .NET Framework to .NET 8 uses these prompts to produce an upgrade checklist, ordered project plan, and validation steps before touching production code. ## Quick Start Ask the agent to analyze all projects in this solution and produce an ordered .NET 8 upgrade plan with dependency and breaking-change analysis.

Frequently Asked Questions about dotnet-upgrade

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

FAQPage Schema
How do I upgrade a .NET Framework project to .NET 8?▼

Start by classifying each project's TargetFramework and SDK usage, then migrate legacy packages.config to PackageReference. Order upgrades from least to most dependent projects, and use .NET Upgrade Assistant or manual upgrades based on project structure.

How to plan the upgrade order for a multi-project .NET solution?▼

Upgrade class libraries first, then APIs and Azure Functions, following the dependency graph from least to most dependent components. Use an incremental strategy with rollback checkpoints and a tracking checklist for build, test, and deployment readiness.

Should I use .NET Upgrade Assistant or upgrade manually?▼

The choice depends on project structure and complexity. .NET Upgrade Assistant automates common migrations and API analysis, while manual upgrades give more control for unusual configurations; the prompts help evaluate which fits each project.

Does this handle NuGet package compatibility during upgrades?▼

Yes, it includes prompts to analyze outdated or incompatible NuGet packages, identify third-party libraries lacking .NET 8 support, review transitive dependency conflicts, and suggest Microsoft-supported alternatives.

What breaking changes should I check when migrating to .NET 8?▼

Check for deprecated APIs and removed namespaces, configuration changes like Startup.cs to Program.cs refactoring, and WebHostBuilder to HostBuilder patterns. Automated scanning with .NET Upgrade Assistant and API Analyzer is recommended.

How do I update Azure DevOps pipelines for a .NET upgrade?▼

Review YAML build definitions for SDK version pinning and update UseDotNet@2 and NuGetToolInstaller tasks. Run validation builds on feature branches before merging, and automate test execution in CI for continuous verification.