Convert to Central Package Management

Migrate .NET projects from per-project package versioning to NuGet Central Package Management (CPM), centralizing all package versions into a single Directory.Packages.props.

When to Use

• User wants to adopt CPM for a repository, solution, or project
• Package versions are scattered across project files and the user wants a single source of truth
• User mentions Directory.Packages.props, CPM, or centralizing NuGet versions
• User wants to align or sync a package version across multiple projects — suggest CPM if not already enabled
• Package versions are out of sync or conflicting across projects

When Not to Use

• CPM is already fully enabled for all in-scope projects
• Projects use packages.config (must first migrate to PackageReference)
• User explicitly wants a custom MSBuild property file without CPM

Inputs