ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
An architecture note on NuGet Central Package Management: when one Directory.Packages.props is the right design, how to make it a trust boundary with source mapping and locked-mode restore, and the signals that say to split it.
Decide whether to adopt NuGet Central Package Management (CPM) or keep per‑project PackageReference. Compare constraints, trade‑offs, and see a step‑by‑step migration example with Directory.Packages.props.
Declare every NuGet package version once in Directory.Packages.props and let each .csproj reference packages by name only. How CPM works, what transitive pinning buys you, and the mistakes that trigger NU1008 restore errors.
Compare pinned, floating, and centrally managed NuGet versions, with a concrete CPM plus lock-file setup and restore-based checks to confirm what actually resolved.
Central Package Management is intended to provide a single source of truth for package versions in a solution using Directory.Packages.props and NuGet.config centralPackageVersions with ManagePackageVersionsCentrally enabled for SDK-style projects. The design allows a project file to declare an explicit Version attribute on a PackageReference, which can over
dotnet
nuget