Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to Nuget Central Package Management #95

Merged
merged 3 commits into from
Mar 19, 2024

Conversation

jonathanou
Copy link
Contributor

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

  • Extract all package reference versions to Directory.Packages.props.
  • Remove version specifications in the original <PackageReference elements.

Testing

Continues to build.

@jonathanou jonathanou changed the title Switch to nuget Central Package Management Switch to Nuget Central Package Management Mar 19, 2024
Copy link
Collaborator

@jryckman jryckman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving now that Pete has approved

Directory.Packages.props Outdated Show resolved Hide resolved
@pakdev pakdev merged commit feadead into ni:main Mar 19, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants