I am currently rebuilding our TFS build infrastructure, we have too many build agents that are just too different, they don’t need to be. So I am looking at a standard set of features on a build agent and the ability to auto provision new instances to make scaling easier. More on this in a future post…
Anyway whilst testing a new agent I had a problem. A build that had worked on a previous test agent failed with the error
Could not load file or assembly ‘Microsoft.TeamFoundation.WorkItemTracking.Common, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
The log showed it was failing to even do a get latest of the files to build, or anything on the build agent.
Turns out the issue was the PowerShell script that installed all the TFS build components and SDKs had failed when trying to install the Azure SDK for VS2013, the Web Deploy Platform was not installed so when it tried to use the command line installer to add this package it failed.
I fixed the issues for the Web PI tools and re-ran the command line to installed the Azure SDK and all was OK.
Not sure why this happened, maybe a missing pre-req put on by Web PI itself was the issue. I know older versions did have a .NET 3.5 dependency. Once to keep an eye on