skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

converting-to-cpm

Convert .NET projects to NuGet Central Package Management with centralized versions.

19|2|Updated May 13, 2026
Search Tags:#NuGet#version management#package resolution#Central Package Management#solution migration
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill converting-to-cpm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: converting-to-cpm
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/common/converting-to-cpm
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill converting-to-cpm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you convert .NET projects and solutions to NuGet Central Package Management (CPM), simplifying package version management and ensuring consistency across your projects.

Core Features & Use Cases

  • Convert to CPM: Migrate projects from per-project package versioning to NuGet Central Package Management.
  • Centralize Versions: Centralize all package versions into a single Directory.Packages.props file for consistency.
  • Resolve Conflicts: Identifies and resolves version conflicts between packages.
  • Use Cases: Ideal for when you want to align package versions across multiple projects or resolve conflicts.

Quick Start

Run the 'converting-to-cpm' skill on your .NET solution or project to enable CPM and centralize package management.

Frequently Asked Questions about converting-to-cpm

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

FAQPage Schema
How do I convert my .NET solution to use NuGet Central Package Management?▼

NuGet Central Package Management (CPM) centralizes all package versions into a single Directory.Packages.props file for consistency. It simplifies package version management and ensures uniform versions across multiple .NET projects within a solution.

Does NuGet Central Package Management work with .NET Core and .NET 5+ applications?▼

Yes, NuGet Central Package Management applies to .NET Core and .NET 5+ applications. It handles version conflict resolution and ensures clean project builds across these targeted frameworks during the migration process.

How do I resolve NuGet package version conflicts across multiple projects?▼

Migrating to Central Package Management aligns package versions across multiple projects by centralizing them into a single Directory.Packages.props file. This approach resolves version conflicts and ensures consistent package resolution throughout your .NET solution.

Why do I need a Directory.Packages.props file for solution migration?▼

You need a Directory.Packages.props file to centralize all NuGet package versions into a single location. This file replaces per-project versioning, ensures consistent package resolution, and eliminates version conflicts across your .NET solution.

What is the best way to centralize NuGet package versioning across projects?▼

The best way to centralize NuGet package versioning is implementing Central Package Management. This approach moves all package versions into a single Directory.Packages.props file, ensuring consistency and resolving version conflicts across projects.

Related Skills

Explore More Software Engineering Skills→
Im5tuIm5tu
6

dotnet-centralise-packages

Centralize NuGet package versions in .NET solutions via Directory.Packages.props.

Community
Intermediate
sayedihashimisayedihashimi
2

convert-to-cpm

Migrate .NET projects to NuGet Central Package Management via Directory.Packages.props.

Community
Advanced
GeneralReasoningGeneralReasoning
4

trivy-offline-vulnerability-scanning

Scan dependency lock files offline with Trivy and JSON output.

Official
Intermediate
seanspiesmanseanspiesman

nuget-manager

Manage NuGet package versions across .NET projects using dotnet CLI.

Community
Advanced