-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty folders in NuGet package meaning #3009
Comments
Would love to understand if this is a DCR, or if we regressed behavior. |
See my email reply, this looked like a DCR. I repro in VS2013. |
This issue comes from the latest comment in #1104 @harikm86 are there any docs that still incorrectly suggest that empty content directories work? If so the doc should be fixed |
Other than this http://docs.nuget.org/Create/Nuspec-Reference, I was not able to find any reference so i believe we are good. the reference here did not pertain to the problem at hand. |
Let's add a clarifying comment on the 2.2 release notes |
Will work with Peter on the text tomorrow. |
@karann-msft : please work with Rob and Peter to update the 2.2 release notes. This will probably be your first commit to NuGet, so congrats in advance :) |
Per NuGet/Home#3009 Removed the line "This feature also enables package authors to easily create empty directories by specifying an empty directory in the NuSpec package." Added a clarification "Empty folders in the "content" folder are ignored when installing the package"
this is fixed |
Per email, please investigate.
The text was updated successfully, but these errors were encountered: