skills.rest
Thorstensen
ThorstensenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

package-management

Centralize NuGet package versions via Directory.Packages.props and dotnet CLI commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams avoid manual XML edits and version drift by centralizing NuGet package versions and guiding package changes through the dotnet CLI.

Core Features & Use Cases

  • Central Package Management (CPM) enables centralized control of versions via Directory.Packages.props.
  • Use dotnet CLI (add/remove/list) to manage packages across projects without editing XML.
  • Share version variables to coordinate related packages and simplify cross-project upgrades.

Quick Start

Enable Central Package Management in your solution and start managing packages with dotnet add, dotnet remove, and dotnet list 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 multiple projects?▼

Central Package Management (CPM) lets you centralize NuGet package versions across multi-project solutions using Directory.Packages.props. This prevents version drift and eliminates manual XML edits.

What is the best way to manage NuGet packages in a dotnet solution without editing XML?▼

The best way to manage NuGet packages without XML edits is using dotnet CLI commands like add, remove, and list. This enforces consistent package operations across all projects safely.

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

Yes, Central Package Management works with dotnet CLI commands. You can use dotnet add, dotnet remove, and dotnet list to manage packages across projects while versions remain centralized in Directory.Packages.props.

How do I update related NuGet packages consistently across different projects?▼

You can update related NuGet packages consistently by sharing version variables in Directory.Packages.props. This coordinates cross-project upgrades and simplifies dependency management across your solution.

Why should I avoid direct XML edits when managing NuGet dependencies?▼

You should avoid direct XML edits to prevent version drift and maintain safety. Guiding package changes through dotnet CLI commands ensures consistent dependency management across multi-project solutions.

When do I need Central Package Management for my dotnet solution?▼

You need Central Package Management when working with multi-project solutions and teams that require consistent package versions. It centralizes versioning and coordinates cross-project package operations.

Related Skills

Explore More Software Engineering Skills→
AratKruglikAratKruglik
9

dotnet-tooling

Standardize .NET SDK usage, package management, and formatting across projects.

Community
Intermediate
tfsugjptfsugjp
3

nuget-manager

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

Official
Intermediate
NotMyselfNotMyself
14

dotnet-cli-essentials

Manage .NET 10 projects with standard dotnet CLI commands.

Community
Basic
seanspiesmanseanspiesman

nuget-manager

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

Community
Advanced