Manually include the CentralPackageVersion files #7705
Merged
Conversation
This file contains 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
To workaround Azure#7490 we are going to simply extract and include the props and targets file from the package directly into our repo.
weshaggard
requested review from
chidozieononiwu,
danieljurek and
mitchdenny
as code owners
pakrym
approved these changes
Sep 20, 2019
jsquire
approved these changes
Sep 20, 2019
|
/azp run net - core |
|
No pipelines are associated with this pull request. |
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.
To workaround #7490
we are going to simply extract and include the props and targets
file from the package directly into our repo.
This should eliminate the issue in #7490 and if the nuget team ever fixes the resolve issue we can consider switching back to using an SDK reference instead.
cc @chidozieononiwu @pakrym