Closed johanclasson closed 6 years ago
I've run into an issue with this recently. It seems that the latest recommended version of NuGet (4.6.2) is dependent on .NET 4.6.
Since this task is set to always use the latest NuGet.exe available a release can (and did) suddenly stop working if an environment does not meet the dependency requirements.
Proposed solution: Lock NuGet version to 4.5.1, or earlier?
Ok. Thanks for reporting this. Either your solution or perhaps stop downloading NuGet and instruct user to use Microsofts NuGet Tool Installer instead. In the latter scenario, DbUp would of course need to be bundled with the DbUp migration-task so that we do not (intentially) break people's builds.
Let's do your solution now and we can think about something better in the long term.
It should be an easy fix changing the download URL for NuGet.
With the latest release (1.1.4) the task comes with a bundled version of DbUp, which will fix your issue since it will no longer be invoking NuGet.
1) Package DLL with task? 2) Get latest minor version? 3) Input field for version?