microsoft/azure-pipelines-tasks VSBuild_dev15tfsu2rtw

MSBuild/VSBuild task update for TFS 2017 RTM and TFS 2017 Update 1

on GitHub

Symptoms

When you use Team Foundation Server (TFS) 2017 RTM or Update 1, and the MSBuild or VSBuild task with Visual Studio 2017 Update 2 or higher. The task is unable to find the installed location of msbuild.exe.

Resolution

The preferred resolution is to update to TFS 2017 Update 2 or higher.

Otherwise the steps below can be used to update the MSBuild and VSBuild tasks:

1. If you are not the TFS team project collection administrator, make sure that you have been added as an agent pool administrator at All Pools level. For more information, see Agent pools.

2. Download the attached PowerShell script Update-MSBuild_VSBuild_TFS2017RTM_thru_U1.ps1.

3. On one your TFS Application Tiers, open a PowerShell console, and then change the current location to the directory where you downloaded the .ps1 file in step 2.

4. To verify that your execution policy allows for the execution of installation scripts, run the following command line:

Set-ExecutionPolicy Unrestricted -Scope Process -Force

1. From a TFS Application Tier, run the installation script against your TFS collection, as follows:

.\Update-MSBuild_VSBuild_TFS2017RTM_thru_U1.ps1 -CollectionUrl http://myserver:8080/tfs/DefaultCollection

Note, agent capabilities

When using TFS 2017 RTM or TFS 2017 Update 1, you may also be experiencing an error when queuing the build:

No agent could be found with the following capabilities: msbuild [...]

or

No agent could be found with the following capabilities: visualstudio [...]

To resolve the capability error, you can either add the missing capability as a user capability or you can download and install the TFS 2017 Update 2 agent.