使用旧版本 NuGet.exe 的 TFS On-Prem 构建代理

Question

We are hosting TFS 2017 Update 2 on-prem, and using on-prem build agents. The latest version of NuGet.exe is currently 4.3.0, but our build agents always default to using v4.0.0. How can I get our build agents to use the latest version of NuGet.exe?

We need to update because NuGet restore is failing when using v4.0.0, but works with v4.3.0, since we are dealing with new .Net Standard 2.0 packages. On our build server I was able to do NuGet.exe update -self to update the NuGet.exe found at C:\\Builds\\_work\\_tool\\NuGet\\4.0.0\\x64\\nuget.exe from 4.0.0 to 4.3.0, but that C:\\Builds\\_work\\_tool directory regularly gets deleted and recreated, so this isn't a persistent workaround.

How can I get our build agents to always use the latest version of NuGet.exe, or at least v4.3.0?

Answer 1

我知道你不应该用链接回答，但这篇文章提供了你需要的所有细节，确认任务确实仍然使用 4.0.0，如何使用 VSTS 和 TFS 2018 你不必担心关于这个（有一个新的 NuGet 安装程序任务）以及如何通过 PowerShell 脚本为 VS 2017.2（及更早版本）重新创建这种任务， 在你的构建中使用最新的 NuGet

Answer 2

Based on Greg's linked answer, but a little bit simpler:

1. Add a step "NuGet Tool Installer" before the other NuGet steps, use ">=5.0.0" for the version and mark "Always download the latest matching version", this should - well - give you the latest stable version
2. Replace the existing "NuGet Installer" steps - this seems to be the default with "NuGet Restore" steps, just copying the settings. They seem to be totally compatible, allowing eg for package config or solution files to be referenced, including pattern matching

That is it. Replacing the "NuGet Installer" that requires you to specify a version with the "NuGet Restore" that just uses the NuGet.exe from the path as set in "NuGet Tool Installer" is easier. Also mind the confusing naming (NuGet Tool Installer/NuGet Installer - the two are rather different).

Having to tinker so much with the not so old TFS 2017 infrastructure is a shame.