I'm migrating to VS2015, and among the migration concerns is that apparently Microsoft has chosen to obsolete the .nuget folder, and the NuGet.exe, being part of the solution. They've also introduced automatic restoration for packages; restoration is well and good, but the resulting bits do my no good locked on my machine. So packaging is more valuable to me, but the Nuspec Packager seems to depend on .nuget. I wonder if there is a workaround for this in the works? Or any suggestions at a migration path? Thank you!
You can create a nuspec-packager.config file that will point to nuget.exe in a location of your choice. See if this works for you. Read more about the settings here: https://github.com/landofjoe/NuspecPackager
I'm migrating to VS2015, and among the migration concerns is that apparently Microsoft has chosen to obsolete the
.nuget
folder, and theNuGet.exe
, being part of the solution. They've also introduced automatic restoration for packages; restoration is well and good, but the resulting bits do my no good locked on my machine. So packaging is more valuable to me, but theNuspec Packager
seems to depend on.nuget
. I wonder if there is a workaround for this in the works? Or any suggestions at a migration path? Thank you!