Open gegenschall opened 9 years ago
:+1: same issue here.
A workaround is to prevent the creation of overlays altogether as explained in #54 .
I run into the same issue. @gegenschall, have you found the cause and solution for this issue?
The cause is the change from NuGet v2 to NuGet v3. The entire API for custom commands has changed, which means the codebase in CoApp.NuGetNativeExtensions
is broken unless you force the use of NuGet client v2 in your repository. It will likely not be an easy fix.
For more details see MSDN docs: https://docs.microsoft.com/en-us/nuget/reference/nuget-client-sdk
and the Dave Glick blog post: https://www.daveaglick.com/posts/exploring-the-nuget-v3-libraries-part-1
After updating Visual Studio 2013 to Update 4 several problems started appearing with one specific package (OpenCV 2.4.10) that uses Overlays:
For some project I have this line in my packages.config in the project root:
Doing
nuget.exe restore
correctly installs the package to$(SolutionDir)packages\
. Upon building of the project it seems that nuget tries to install an overlay packge which succeeds but it gets installed in the wrong location thus .lib and .dll files cannot be found when linking. The error message is:It really isn't there, its at the top-level package source location or sometimes at the project root. How do I fix this?