i have VS2012, VS2013 and VS2015 installed (as well as 20; blame VS's c-runtime, build tools, debug dll and legacy sdk dependencies...).
it is essentially a race condition between how fast the nuget package installer can make file changes before the source control monitoring update check occurs in the background. So i technically use nuget in both 20 at the moment.
Adding @rrelyea @yishaigalatzer to answer your questions on associating dependent files with a nuget package. If you find this to be the cause at your end, we would definitely want to fix the scenario.
Would also help to provide some steps (doesn't matter what package it is).
Also in this case the files in the content directory had not changed between packages, so i am not sure if when it added them back it would have picked up any differences had there been any.
i guess i should also clarify, just in case, since my original question as to whether this was the extension of the related codeplex issue was not technically responded to, to make sure we are all on the same page.
i will attempt to recreate the issue with another project.
i guess i could also ask: What is the correct way to associate dependent files with a nuget package?
So technically the package is installed but the dependent files must be updated manually after the fact once the Pending changes are resolved. i definitely still see this issue with the latest builds.
So technically the package is installed but the dependent files must be updated manually after the fact once the Pending changes are resolved. As such undoing the Pending Changes replaces the files with those from the server again.