I’ve been testing a System wide windows environment variable ‘EnableNuGetPackageRestore’ =‘true’ and it didn’t seem to work with nuget actions in continua ( I haven’t tested the continua user environment variables option at this stage). It seemed that editing %Source.xyz%\src.nuget\NuGet.targest seemed to work, to allow VS to build the solution rather than using Nuget actions.
[code]<!-- Determines if package restore consent is required to restore packages --> <RequireRestoreConsent Condition=" ‘$(RequireRestoreConsent)’ != ‘false’ ">false</RequireRestoreConsent> [/code]
Now I’ve seen there is a -RequireConsent argument for Nuget Install, maybe that would be the best change in the Continua Nuget Install action to help jump over the issue.
Hi Jamie
I’m not sure that the command line option would help :
http://blog.nuget.org/20120907/recent-changes-to-package-restore-consent.html
It looks to me like you are trying to disable the need for consent… which entirely makes sense in a CI scenario. From what I can tell from the above blog post, that should be the default behavior, but it’s not what I see here.
I have added support for setting Environment variables on the Nuget actions, and I have added an EnablePackageRestore to the nuget install action… just need to do some testing on it though… not sure it will be enough.
BTW, if you change environment variables after the continua agent service is started, it will not see the changes… that’s just how windows processes work
(they get their environment block when they start).
I’ve been testing, but I’m not sure what I am doing wrong, as it seems to work fine no matter what settings I have for package restore.