Enable central NuGet package version management #708
Merged
+100
−55
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a Directory.Package.props file to enable central package management. This has 2 main advantages: - Changes to versions only needs to be done 1 file (.csproj files are unchanged for NuGet updates) - All projects use the same NuGet package version.
|
@vbaderks Many thanks! I am looking forward to the next PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a Directory.Package.props file to enable central package management.
This has two advantages:
The NuGet package versions itself are not changed in this PR to keep the scope limited to the introduction of a Directory.Packages.props file. This is a first step to resolve #704.