nuget-manager

Topics in the source

• NuGet Manager
• Overview
• Prerequisites
• Core Rules
• Workflows
• Adding a Package
• Removing a Package
• Updating Package Versions

This skill ensures consistent and safe management of NuGet packages across .NET projects. It prioritizes using the dotnet CLI to maintain project integrity and enforces a strict verification and restoration workflow for version updates. .NET SDK installed (typically .NET 8.0 SDK or later, or a version compatible with the target solution). dotnet CLI available on your PATH. jq (JSON processor) OR PowerShell (for version verification using dotnet package search). 1. NEVER directly edit .csproj, .props, or Directory.Packages.props files to add or remove packages. Always use dotnet add package and dotnet remove package commands. 2. DIRECT EDITING is ONLY permitted for changing versions of existing packages. 3. VERSION UPDATES must follow the mandatory workflow: Verify the target version exists on NuGet. Determine if versions are managed per-project (.csproj) or centrally (Directory.Packages.props). Update the version string in the appropriate file. Immediately run dotnet restore to verify compatibility. Use dotnet add [ ] package [--version ]. Example: dotnet add src/MyProject/MyProject.csproj package Newtonsoft.Json Use dotnet remove [ ] package . Example: dotnet remove src/MyProject/

This is an excerpt. Refer to the complete source and its current requirements.