What are the requirements for using CPM with this skill?

CPM requires the .NET SDK 6.0.300 or later, NuGet 6.2 or later, and Visual Studio 2022 17.2 or later.

Why shouldn't I edit .csproj files directly for packages?

Using the dotnet CLI validates that the package exists, resolves correct versions, handles transitive dependencies, and ensures compatibility with Central Package Management, which manual XML editing often bypasses or breaks.

Can this skill help identify insecure dependencies?

Yes, it includes specific CLI commands and workflows to list vulnerable, deprecated, and outdated packages across your entire .NET solution.

How does this skill handle related package groups?

It utilizes shared version variables in the CPM configuration, allowing you to update an entire suite of related packages (like xUnit or Aspire) by changing a single property value.

What are the benefits of Central Package Management (CPM)?

CPM centralizes all package versions in a single file (Directory.Packages.props), eliminating version drift across projects and simplifying the update process for the entire solution.

.NET NuGet & CPM Manager

Name: .NET NuGet & CPM Manager
Author: bbsbot

bybbsbot

•

Herramientas para Desarrolladores

Manages NuGet dependencies and Central Package Management (CPM) using dotnet CLI best practices to ensure solution-wide version consistency.

This skill automates and enforces best practices for .NET dependency management, specifically focusing on Central Package Management (CPM) and the dotnet CLI. It eliminates error-prone manual XML editing by prioritizing CLI commands for adding, removing, and updating packages. By utilizing shared version variables within Directory.Packages.props, it ensures version synchronization across large multi-project solutions, simplifies updates for related package suites like Akka.NET or OpenTelemetry, and provides structured workflows for troubleshooting restore failures and auditing for vulnerable dependencies.

Características Principales

01Comprehensive auditing for outdated, deprecated, or vulnerable packages

02Implementation of shared version variables for related package groups

031 GitHub stars

04CLI-first dependency management to prevent project file corruption

05Advanced troubleshooting workflows for NuGet restore and dependency conflicts

06Automated Central Package Management (CPM) configuration and maintenance

Casos de Uso

01Synchronizing versions for complex package suites across multiple microservices

02Automating the identification and resolution of transitive dependency conflicts

03Migrating a legacy .NET solution to Central Package Management for better version control

Características Principales

01Comprehensive auditing for outdated, deprecated, or vulnerable packages

02Implementation of shared version variables for related package groups

031 GitHub stars

04CLI-first dependency management to prevent project file corruption

05Advanced troubleshooting workflows for NuGet restore and dependency conflicts

06Automated Central Package Management (CPM) configuration and maintenance

Casos de Uso

01Synchronizing versions for complex package suites across multiple microservices

02Automating the identification and resolution of transitive dependency conflicts

03Migrating a legacy .NET solution to Central Package Management for better version control