skills.rest
luongnguyenminhan
luongnguyenminhanCOMMUNITY
Explore all skills by this author →
GitHub

package-management

Centralize NuGet package versions across .NET projects using CPM and the dotnet CLI.

Updated Feb 17, 2026
Search Tags:#versioning#dotnet#nuget#package-management#dotnet-cli#central-package-management
One-click install
npx skills add https://github.com/luongnguyenminhan/EmployeeDemoCS --skill package-management-luongnguyenminhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: package-management
Source: https://github.com/luongnguyenminhan/EmployeeDemoCS/tree/main/.github/skills/package-management
Command: npx skills add https://github.com/luongnguyenminhan/EmployeeDemoCS --skill package-management-luongnguyenminhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes NuGet package versions across multi-project solutions using CPM and the dotnet CLI.

Core Features & Use Cases

  • Add, remove, or update packages via dotnet CLI commands (dotnet add package, dotnet remove package, dotnet list package).
  • Enable Central Package Management by creating and configuring Directory.Packages.props to centralize version management across projects.
  • Apply Shared Version Variables to keep related packages in sync and reduce version drift.
  • Troubleshoot package conflicts and restores in large solutions.

Quick Start

Initialize CPM at the solution root and manage all package versions through dotnet CLI commands.

Frequently Asked Questions about package-management

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

FAQPage Schema
How do I centralize NuGet package versions across a multi-project .NET solution?▼

To centralize NuGet package versions, you enable Central Package Management by creating a Directory.Packages.props file at the solution root and managing package references through the dotnet CLI. This ensures version consistency across all projects.

What is Central Package Management and when do I need it for .NET solutions?▼

Central Package Management is a feature that consolidates NuGet version control into a single Directory.Packages.props file. You need it for large .NET solutions to prevent version drift and simplify package updates across multiple projects.

Can I use the dotnet CLI to add and remove packages when Central Package Management is enabled?▼

Yes, you can use the dotnet CLI to add, remove, and list packages when Central Package Management is enabled. Commands like dotnet add package and dotnet remove package automatically update the centralized configuration without manual file editing.

How do I resolve NuGet package conflicts in a large .NET solution?▼

To resolve NuGet package conflicts in a large .NET solution, you apply shared version variables and use dotnet CLI commands to enforce consistent package versions. This approach eliminates version mismatches and troubleshooting restore issues.

Do I need any specific tools to configure Central Package Management?▼

You need the dotnet CLI to configure Central Package Management. The process involves creating a Directory.Packages.props file at the solution root and executing dotnet CLI commands to manage your package references and versions.

Related Skills

Explore More Software Engineering Skills→
sayedihashimisayedihashimi
2

dotnet-tooling

Automate .NET SDK installation, workloads, and MSBuild tooling setup.

Community
Advanced
BridgingIT-GmbHBridgingIT-GmbH
7

dotnet-package-management

Manage NuGet dependencies across multi-project solutions using CPM and dotnet CLI.

Official
Intermediate
NikiforovAllNikiforovAll
137

dotnet-dependency

Inspect .NET project dependencies using dotnet CLI commands.

Community
Intermediate
riandeoliveirariandeoliveira

package-management

Manage NuGet packages across .NET solutions using dotnet CLI and CPM.

Community
Intermediate