I'm new to nuget so I'm not sure I'm doing it right but I've got a .proj file being invoked by a custom build step in a .vcxproj (native c++ project) and the .proj invokes a task from the pack. I had been installing the pack on the build platform and importing the targets file using the installation path explicitly. Switching the the nuget has lots of benefits but....
1) the installation is not "sticky" -- after installing it in the host project the files are downloaded but the project fails to remember that it is installed. So when I get the sources onto a virgin build machine the pack nuget isn't there and the subordinate project fails.
2) no macro is created pointing to the installed pack in the host project so I still have to use an explicit (though relative) path.
Long run, I'd like to change the subordinate .proj file into an embedded target in the host project but with the way the nuget operates that's not happening.
I'll pull a fork and see what I can do to fix this myself.
I'm new to nuget so I'm not sure I'm doing it right but I've got a .proj file being invoked by a custom build step in a .vcxproj (native c++ project) and the .proj invokes a task from the pack. I had been installing the pack on the build platform and importing the targets file using the installation path explicitly. Switching the the nuget has lots of benefits but....
1) the installation is not "sticky" -- after installing it in the host project the files are downloaded but the project fails to remember that it is installed. So when I get the sources onto a virgin build machine the pack nuget isn't there and the subordinate project fails.
2) no macro is created pointing to the installed pack in the host project so I still have to use an explicit (though relative) path.
Long run, I'd like to change the subordinate .proj file into an embedded target in the host project but with the way the nuget operates that's not happening.
I'll pull a fork and see what I can do to fix this myself.