Using "TFS" extension with TFS 2012

Hello,

We are currently using the "TFS2012" BuildMaster extension. We know that it is not supported anymore and had recently tried to switch over to the "TFS" extension.

When attempting to use the Create TFS Build action from the "TFS" extension, we had received the following exception:

An unhandled exception occurred while executing this action: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.TeamFoundation.Client, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.TeamFoundation.Client, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at Inedo.BuildMasterExtensions.TFS.CreateTfsBuildAction.Execute()
at Inedo.BuildMaster.Extensibility.Actions.ActionBase.ExecuteInternal(IActionExecutionContext context, ExtensionConfigurerBase extensionConfigurer, Boolean resumeNextOnError, Boolean logErrorsAsWarnings)

We do not have Visual Studio 2013 on the controller that is calling the Create TFS Build action, but do have Visual Studio 2012. Is it be possible to change the "TFS" extension to point to the Visual Studio 2012 binaries rather than the 2013 binaries?

Thank you,
Kevin

Product: BuildMaster
Version: 4.8.4

Hi Kevin,

The "TFS" extension should work with 2010, 2012, 2013, and 2015; the .dll we create does not reference a specific version of the TFS .dlls, as you can see here: https://github.com/Inedo/bmx-tfs/blob/master/TFS.csproj#L66

Note that your error message is referencing "Version=12.0.0.0" (which is Visual Studio 2013); this means that one of the (many) TFS v12 .dlls were already successfully loaded into memory, but the remaining libraries could not be. This could happen if some other components/tools, like MSBuild extensions, were installed.

Can you just Team Viewer 2013? This will give you a complete set of libraries, and then the action will work.

Thanks Alana! We will go down the route of installing Team Explorer 2013.

i have 2015 team explored installed but not succeeded in same schenario.