This repository has been archived by the owner on Jan 21, 2022. It is now read-only.
Fix NuGet package format #309
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
|
Can we talk on gitter? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
#308 will make this fix obsolete.
The NuGet packages produced by Vlc.DotNet are invalid. The assemblies are located in
lib\{TFM}\AnyCPU\, but the NuGet specifications do not allow for anAnyCPUsubfolder. Instead, the libraries should just go inlib\{TFM}.I hit this on Visual Studio 2017; perhaps newer NuGet versions are a bit more strict about the folder structure.
This PR fixes that.
Fixes #276
Obsoletes #300
Fixes NuGet/Home#4417
Fixes NuGet/Home#4259
Fixes NuGet/Home#5678