nuget-manager

Verify, update, and restore NuGet package versions in .NET projects.

18|3|Updated Jul 3, 2020
One-click install
npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill nuget-manager-jguadagno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuget-manager
Source: https://github.com/jguadagno/jjgnet-broadcast/tree/main/.agents/skills/nuget-manager
Command: npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill nuget-manager-jguadagno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Managing NuGet packages in .NET projects can be complex and error-prone, especially when handling multiple dependencies and versions manually.

Core Features & Use Cases

  • Version Control: Ensures consistent package versions across solutions by managing dependencies centrally or per project.
  • Workflow Enforcement: Guides users through safe workflows for adding, removing, and updating NuGet packages, reducing errors.
  • Use Case: Developers updating a critical package like Newtonsoft.Json to a specific version can verify its existence and update all relevant project files automatically, then verify stability with restore.

Quick Start

Use the nuget-manager skill to update the Newtonsoft.Json package to version 13.0.3 across the entire solution.

Frequently Asked Questions about nuget-manager

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

FAQPage Schema
How do I update a NuGet package to a specific version across a .NET solution?

To update a NuGet package across a .NET solution, you can use this skill to verify the package existence, automatically update version references in all relevant project files, and restore dependencies to ensure stability.

What is the safest way to manage NuGet dependencies in large .NET codebases?

Safe NuGet dependency management in large .NET codebases requires enforcing standards to prevent manual file edits, promoting consistent version handling centrally or per project, and verifying restores after updates.

Can I manage NuGet package versions centrally for multiple .NET projects?

Yes, you can manage NuGet package versions centrally across multiple .NET projects, ensuring consistent dependency versions are maintained throughout the entire solution without manual configuration file edits.

Why should I avoid manually editing project files when updating dotnet packages?

Manually editing project files when updating dotnet packages introduces errors and inconsistencies; enforcing an automated workflow for adding, removing, and updating NuGet packages reduces errors and maintains version control standards.

What's the best way to verify a NuGet package exists before adding it to my project?

The best way to verify a NuGet package exists before adding it to your project is to use an automated workflow tool that checks package existence, updates version references, and restores project dependencies sequentially.