coapp-developers team mailing list archive

[Gonçalo Lopes <goncaloclopes@xxxxxxxxx>]

Hey guys,

I've recently updated to the latest version of CoApp development (2.4.493)
and I started experiencing a weird behavior with overlay packages.

I first built a native package with overlays and verified that it deployed
fine under all platform/architecture/configuration combinations.

In preparation for pushing to the NuGet gallery, I updated my NuGet.exe in
the PATH to the latest release and set the API key.

After this step I pushed everything to NuGet and retried the installation
from the remote server.

To my surprise, I started getting this warning: "warning : Overlay Package
'OpenCV.overlay-Win32_v110_Debug v2.4.9' installed correctly, but the nupkg
file 'c:\Users\Gonçalo\documents\visual studio
2012\Projects\ConsoleApplication6\packages\OpenCV.2.4.9\OpenCV.overlay-Win32_v110_Debug.2.4.9.nupkg'
is not in the expected location."

Basically for some reason the overlay packages got installed in the
directory where the ".csproj" is, rather than the package root directory.
Also predictably the build failed since files were not where they were
supposed to be.

After painfully backtracking all my steps, I traced the cause down to my
upgraded version of NuGet.exe in PATH.

Apparently CoApp uses either the NuGet client that comes with the package
or the one in PATH, whichever has the largest version. When the NuGet
client embedded in the package was the highest version, everything was
fine. However, when I upgraded the NuGet.exe in my PATH, CoApp started
using that and then I got this behavior.

I verified this was the case by removing NuGet from the PATH and retrying
the installation: it works. If I put it back in the PATH again, I go back
to this weird behavior.

I already confirmed I get this with both VS 2012 and 2013. Any idea what
could cause this behavior at all?

Why should the overlay install location change depending on where the NuGet
client is?

For now I'm trying to get the NuGet support team to retract my package, but
this is a big source of concern, since it may mean deployment can break
depending on machine configuration...

By the way, the NuGet version in PATH was 2.8.1.

Hope you can help me out. Thanks,
Gonçalo