managing-package-references

Manage .NET package references and dependencies in project files.

19|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill managing-package-references
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-package-references
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/common/managing-package-references
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill managing-package-references

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management of .NET package references and dependencies, automating the process of adding, updating, and removing packages from project files.

Core Features & Use Cases

  • Package Management: Handles PackageReference, ProjectReference, and FrameworkReference items in .NET project files.
  • Supports CPM: Integrates with Central Package Management (CPM) and standard package management.
  • Use Case: For instance, update a package version across multiple projects by modifying a single file in CPM mode.

Quick Start

Use the 'managing-package-references' skill to update the Newtonsoft.Json package to the latest version in all your .NET projects.

Frequently Asked Questions about managing-package-references

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

FAQPage Schema
How do I update NuGet package versions across multiple .NET projects at once?

You can update NuGet package versions across multiple projects by using Central Package Management (CPM) to define versions in a single file, which the skill modifies directly to synchronize dependencies.

How do I add or remove ProjectReference and FrameworkReference items in .NET project files?

Adding or removing ProjectReference and FrameworkReference items is handled by modifying the .NET project files directly, allowing you to configure project dependencies and framework targeting.

Does this approach support Central Package Management for .NET applications?

Yes, Central Package Management (CPM) is fully supported alongside standard package management, enabling centralized control over NuGet dependency versions throughout your solution.

What is the best way to manage PackageReference items in .NET project configuration?

Managing PackageReference items is best handled by automating the addition, removal, and updates directly within the project files to streamline dependency configuration.

Can I use this to switch from standard package management to Central Package Management?

Yes, you can manage CPM configurations to transition from standard package management by updating your project files to reference a central package version file.