Using the latest NuGet in your build
Sep 30, 2017Alex Mullans

Summary
This post addresses the challenge of using newer versions of NuGet (4.1+) with Team Build in Visual Studio Team Services (VSTS) and Team Foundation Server (TFS). It introduces the 'NuGet Tool Installer' task for VSTS and TFS 2017 Update 3+, which automatically installs the required NuGet version. For older TFS versions (TFS 2017 Update 2 and earlier), a workaround involving a PowerShell script to fetch and use a specific NuGet version before the 'NuGet Restore' or 'NuGet' task is provided. This ensures compatibility with new .NET Core and .NET Standard project types and meets the NuGet.org protocol version requirement for pushing packages.
More from the Azure Pipelines Agent Operating System Support trail
- April Patches for Azure DevOps Server and Team Foundation Server
- CDN Domain URL change for Agents in Pipelines
- Announcing the General Availability of Managed DevOps Pools (MDP) for Azure DevOps
- Announcing Public Preview of Managed DevOps Pools (MDP) for Azure DevOps
- End of support for Azure Pipelines agents running on CentOS 6, Debian 4.9, Fedora 32, Ubuntu 16, macOS 10.14, and older versions