Fixup nuspecs master #18215
Merged
Fixup nuspecs master #18215
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
|
Don't reference private repos from public PRs 😉 |
dougbu
approved these changes
Oct 3, 2019
There was a problem hiding this comment.
@AndriySvyryd what changed is we're now building with NuGet (.NET Core SDK) infrastructure that checks the frameworks against the files in a package. @wtgodbe fixed that in 'release/3.0' but we need fewer or no workaround in 'release/3.1' and 'master' because the TFMs are different.
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.
In release/3.0, we needed placeholder files for NetStandard1.3 and NetCoreApp2.1 in these 2 nuspecs, but that's not the case in release/3.1 or master. Their existence caused nuget package validation to fail.
Manual cherry-pick of #18214, in case that one has to wait for preview2.