skills.rest
woutervanranst
woutervanranstCOMMUNITY
Explore all skills by this author →
𝕏@woutervanranstGitHub

package-management

Manage NuGet packages with centralized CPM versioning and dotnet CLI workflows.

1|Updated Mar 10, 2026
Search Tags:#nuget#package-management#dependency-management#project-configuration#dotnet-cli#cpm
One-click install
npx skills add https://github.com/woutervanranst/Arius7 --skill package-management-woutervanranst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: package-management
Source: https://github.com/woutervanranst/Arius7/tree/main/.agents/skills/package-management
Command: npx skills add https://github.com/woutervanranst/Arius7 --skill package-management-woutervanranst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes NuGet package management by enforcing centralized versioning with Central Package Management (CPM) and safe dotnet CLI workflows, eliminating manual XML edits and version drift.

Core Features & Use Cases

  • Centralized versioning with Directory.Packages.props for consistent package versions across projects
  • Use dotnet add, dotnet remove, and dotnet list to manage packages without editing XML
  • Resolve conflicts and simplify multi-project dependency management

Quick Start

Configure CPM at the solution root and start using dotnet CLI to add, remove, and update packages across projects.

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 multiple .NET projects?▼

Centralize NuGet package versions by enabling Central Package Management (CPM) with a Directory.Packages.props file at your solution root. This enforces consistent dependency versions across all projects, eliminating version drift without requiring manual XML edits.

Can I use dotnet CLI commands to manage packages without manually editing XML files?▼

You can manage NuGet packages entirely through safe dotnet CLI workflows using add, remove, list, and restore commands. This approach completely avoids manual XML edits while maintaining centralized versioning via CPM and Directory.Packages.props configuration.

What is Central Package Management (CPM) and when do I need it for dependency management?▼

Central Package Management (CPM) is a NuGet feature that standardizes dependency versioning across multiple .NET projects via Directory.Packages.props. You need it when managing a solution environment requiring consistent package versions to prevent version drift and simplify multi-project dependency conflicts.

How do I safely upgrade NuGet packages across all projects in a .NET solution?▼

Upgrade NuGet packages by updating the shared version variable in Directory.Packages.props and running dotnet restore. CPM ensures all projects instantly reference the new version, simplifying multi-project dependency upgrades without manual XML edits or individual project modifications.

Does Central Package Management work with the dotnet CLI for adding and removing dependencies?▼

Central Package Management fully supports routine dotnet CLI workflows including add, remove, list, and restore commands. You can safely manage dependencies across multiple .NET projects without manual XML edits while CPM enforces consistent centralized versioning.

Related Skills

Explore More Software Engineering Skills→
rudironsonirudironsoni

dotnet-scaffold-project

Generates .NET projects withsrc/tests layout and CI-ready configuration files.

Community
Advanced
BridgingIT-GmbHBridgingIT-GmbH
7

dotnet-package-management

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

Official
Intermediate
luongnguyenminhanluongnguyenminhan

package-management

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

Community
Intermediate
tfsugjptfsugjp
3

nuget-manager

Manage NuGet packages across .NET projects using the dotnet CLI.

Official
Intermediate