dotnet-package-management

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

7|4|Updated Dec 12, 2023
One-click install
npx skills add https://github.com/BridgingIT-GmbH/bITdevKit --skill dotnet-package-management-bridgingit-gmbh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-package-management
Source: https://github.com/BridgingIT-GmbH/bITdevKit/tree/main/.agents/skills/dotnet-package-management
Command: npx skills add https://github.com/BridgingIT-GmbH/bITdevKit --skill dotnet-package-management-bridgingit-gmbh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage NuGet packages across a solution using Central Package Management (CPM), the dotnet CLI, and dotnet-outdated to keep dependencies consistent and up to date without editing XML files.

Core Features & Use Cases

  • Centralized version management with CPM to avoid per-project version drift.
  • Safe package upgrades using dotnet CLI and dotnet-outdated with validation and restoration steps.
  • Diagnostics workflow for restore issues and dependency conflicts across multiple projects.

Quick Start

Run a CPM-enabled workflow at the solution root and use dotnet CLI commands to add, list, upgrade, and restore packages.

Frequently Asked Questions about dotnet-package-management

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

FAQPage Schema
What is Central Package Management and how does it prevent NuGet version drift?

Central Package Management (CPM) controls NuGet versions across a multi-project solution from a single location. It prevents version drift by eliminating per-project version overrides, ensuring consistent dependencies without manual XML edits.

How do I upgrade NuGet packages across a solution using the dotnet CLI?

To upgrade NuGet packages using the dotnet CLI, run a CPM-enabled workflow at the solution root with dotnet-outdated. This applies safe upgrades with validation and restoration steps to resolve dependencies across projects.

Can I diagnose NuGet restore issues and dependency conflicts across multiple projects?

Yes, you can diagnose NuGet restore issues and dependency conflicts across multiple projects using a diagnostics workflow. It applies centralized version control and validation to identify and resolve multi-project dependency conflicts.

What is the best way to manage NuGet dependencies in a multi-project solution?

The best way to manage NuGet dependencies in a multi-project solution is combining Central Package Management with the dotnet CLI. This centralizes version control and automates safe upgrades without editing XML files.

Does dotnet-outdated support rollback considerations if a package upgrade fails?

Yes, using dotnet-outdated with the dotnet CLI includes rollback considerations. It applies safe package upgrades with validation and restoration steps, providing clear guidance to revert if dependency conflicts or restore issues occur.