Skip to main content
N
All NuGet guides

Practical workflow

Audit Central Package Management versions

Central Package Management makes version decisions visible in one place. That also makes it the best input for reviewing upgrade pressure and package risk across a multi-project solution.

Audit Directory.Packages.props

Workflow

  1. 1

    Open the shared version file

    Use the Directory.Packages.props file rather than an individual project file, so the audit begins from the centrally declared versions.

  2. 2

    Prioritise changes by impact

    Start with advisories and deprecations, then inspect major updates and packages shared by the most projects.

  3. 3

    Validate framework-specific resolution

    A central version can resolve differently across target frameworks. Confirm the resulting graph with restore and tests for each supported target.

  4. 4

    Upgrade in a controlled batch

    Keep related package families together, document breaking changes and publish the audit result with the version-file change.

What this workflow gives you

  • One review queue for versions used throughout a solution.
  • A way to distinguish shared dependency risk from single-project choices.
  • A repeatable input for upgrade pull requests and release checks.

Choose packages with context

JSON libraries for .NETLogging packages for .NETTesting frameworks for .NET

Data, method and limits

Sources: the project file you select and the public NuGet v3 registry. Refresh: registry metadata is queried while the tool runs; your file stays in the browser. Method: the workflow turns declared versions and published package metadata into a review queue. Limit: The browser audit reads declared package versions and published registry metadata. It does not evaluate MSBuild conditions, private feeds, lock files or application behaviour.