Centrally manage NuGet dependencies and its versions #4181
Closed
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
|
Thanks Nirmal4G for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌 |
ghost
requested review from
ghost
added
the
feature request 📬
|
The build failed, since, there's an issue with |
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
4 times, most recently
from
a3e0d80 to
7110aee
Compare
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
6 times, most recently
from
48c7eb2 to
430b18b
Compare
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
4 times, most recently
from
4a34b2c to
a501027
Compare
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
from
a501027 to
6dc6487
Compare
6 tasks
|
I have extracted unrelated refactoring into its own PR: #4234; I'll rebase this on latest once the PR is merged. |
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
3 times, most recently
from
e3ae65e to
668f26e
Compare
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
from
fbfb605 to
ed4abe6
Compare
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
from
d5fa86f to
a4bfab8
Compare
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
4 times, most recently
from
7823c50 to
1561c58
Compare
7 tasks
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
9 times, most recently
from
91dce2a to
f49185c
Compare
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
from
f49185c to
02feec9
Compare
Renormalize new lines and remove BOM from new files
- Refactor Project files - Refactor Markdown files - Remove unnecessary files - Use latest NuGet and config - Fixup UAP/Windows TFM versions
The new Output paths point to...
Build: `~build\...`
Restore: `~build\ext`
Publish: `~publish\...`
Pack: `~packages\{bin,obj}`
Update package versions. Use Static Graph restore when applicable. Manage Packages Centrally using NuGet's CPVM feature.
Use "MSBuild.NET.Extras.Sdk" instead of "MSBuild.Sdk.Extras" for projects. This replacement package contains fixes around UWP project setup and build!
Nirmal4G
force-pushed
the
feature/nuget-cpvm
branch
from
47a1b6c to
9a6802c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #4180
Know more about NuGet's Central Package Version Management (CPVM) feature.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
NuGet package references are spread across project files. It is difficult to track versions and upgrade them properly.
What is the new behavior?
Enables NuGet's upcoming feature to manage package versions centrally using
Directory.Packages.propswith the following item spec to store a package version.PR Checklist
Please check if your PR fulfils the following requirements:
Other information
rebaseon latestHEADand then commit, without updating from the latestHEAD.Merge pull request #xxxx from repo/branch, and commit message to either PR message or messages of individual commits. Theauto-mergebot does this by default.