-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Enable NuGet Central Package Management #5420
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It took me a while to catch this, but this file is independent of Directory.Build.props
...osoft.Management.Configuration.Processor/Microsoft.Management.Configuration.Processor.csproj
Outdated
Show resolved
Hide resolved
src/PowerShell/Microsoft.WinGet.Client.Engine/Microsoft.WinGet.Client.Engine.csproj
Outdated
Show resolved
Hide resolved
<PackageVersion Include="System.Private.Uri" Version="4.3.2" /> | ||
<PackageVersion Include="System.Security.Principal.Windows" Version="5.0.0" /> | ||
<PackageVersion Include="System.Text.RegularExpressions" Version="4.3.1" /> | ||
<PackageVersion Include="xunit" Version="2.4.2" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just realized that we use both nunit and xunit in different projects, which seems a bit weird
This pull request introduces the NuGet Central Package Management feature to streamline dependency management. Key benefits and changes include:
Centralized Version Management: All NuGet package versions are now managed centrally in the
Directory.Packages.props
file. This ensures consistency across all projects in the repository.Simplified Project Files: The individual project files are simplified, as they no longer need to specify version numbers for NuGet packages. This change reduces duplication and the potential for version conflicts.
Ease of Updating Dependencies: Updating a package version is now a matter of changing it in one place, making the process of keeping dependencies up-to-date more straightforward and less error-prone.
(Description copied from the automated PR to the internal repo :D )
Microsoft Reviewers: Open in CodeFlow