Switch to Nuget Central Package Management #95
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Justification
Since .NET 6.0.300, there is a new Central Package Management (CPM) feature that allows tracking nuget versions centrally. CPM relies on a new
Directory.Packages.props
file to maintain the list of nuget package versions and by default all projects cannot specify nuget versions—the build will break otherwise.We should switch to using CPM to help simplify our build management, and ensure that all projects are using the same nuget package versions—switching to CPM will also make updating nuget packages in the future a lot easier.
Implementation
Directory.Packages.props
.<PackageReference
elements.Testing
Continues to build.