dotnet-update-packages

This skill applies when the user:

• Asks about outdated NuGet packages
• Wants to update dependencies in a .NET project
• Mentions package version upgrades
• Discusses dependency management in .NET

1. List outdated packages (including transitive) using:

```bash

dotnet package list --outdated --include-transitive --format json

```

1. Check for empty results - If no outdated packages found, inform the user and stop

1. Parse output to identify:

- Projects with outdated packages

- Whether each package is direct or transitive

1. Analyze project dependencies by reading elements in each csproj

1. Present findings in a readable format showing project, package name, current → latest version

1. Confirm with user before making changes - ask which option:

- All packages

- Specific packages by name

- Cancel

1. Update packages per project with --project parameter:

- Update leaf projects first (no dependencies)

- Then update dependent projects

- Independent branches can run in parallel

```bash

dotnet package update --project

```

1. Verify with dotnet build

1. If build fails, ask user:

- Fix automatically (review errors, apply fixes)

- Fix manually (show errors, let user handle)

1. Report results - summarize what was updated and the final build status

| Command | Purpose |

|---------|---------|

| dotnet package list --outdated --include-transitive --format json | List outdated packages (incl. transitive) |

| dotnet package update --project | Update specific package in project |

| dotnet package update --project | Update all packages in project |

• Direct: Explicitly in csproj. Update directly.
• Transitive: Pulled in by dependencies. Marked [T] in output.

- To update: update the parent package, or add direct reference to pin version

• If dotnet package list fails: Check if we're in a .NET project directory
• If dotnet package update fails for a specific package: Report it and continue with others
• If build fails after updates:

1. Parse the build errors

2. Ask user: fix automatically or manually?

3. If automatic: analyze errors and apply fixes

4. Re-run build to verify

• Requires .NET 10+ SDK for dotnet package update
• Always use --project parameter to update per-project
• Update in dependency order: leaves first, then dependents
• Always confirm with user before updating
• Run build after updates to catch breaking changes