In the latest beta, Nuget install actions pass the FileConflictAction parameter, which is not supported with the version of Nuget that ships with the agent (or the latest, 2.8.2).
It’s odd because it’s still listed in the command-line documentation on the NuGet site, but the action fails because the parameter is not supported.
Hi Drew,
Thanks for reporting this. It seems that the NuGet install command line never supported this option. The option has been removed from the latest beta.
This is fixed now, thanks.