nuget-manager

To update NuGet package versions, the skill detects whether versions are managed per-project in .csproj files or centrally in Directory.Packages.props, then updates the correct location and runs dotnet restore to verify compatibility.

The best way to manage NuGet dependencies safely is by enforcing dotnet CLI commands for package additions and removals, restricting direct file edits to version changes only, and validating that versions exist on NuGet before applying them.

Yes, NuGet package management works with centralized Directory.Packages.props files by automatically detecting the central configuration and updating the correct file with validation rather than editing individual .csproj files.

You should use the dotnet CLI instead of editing .csproj files directly because manual edits are error-prone; the CLI enforces a safe, auditable workflow for adding, removing, and updating NuGet package versions with validation.

To verify a NuGet package version exists before adding it, the skill checks the NuGet registry to confirm version availability, updates the appropriate .csproj or Directory.Packages.props file, and runs dotnet restore to verify compatibility.

If a NuGet package restore fails after a version update, it indicates a compatibility issue; the workflow runs dotnet restore specifically to verify compatibility after applying validated version changes to .csproj or Directory.Packages.props files.