TFS Integration Tools – Issue: “This tool requires the TFS client object model”

  • Article

Issue

When installing the TFS Integration Tools on a machine that only has the Team Explorer installed, the installation fails with the error “This tool requires the TFS client object model”.
image

This has been identified as an issue and will be considered for resolution in future versions of the TFS Integration Tools.

Applies to

  • TFS Integration Tools, version 2.2, March 2012
  • TFS Team Explorer 2012

Finding

The WiX script for the above mentioned TFS Integration Tools is looking for pre-requisites for different registry key for Team Explorer 2012 compared to earlier versions. This key will not be created when Team Explorer 2012 is installed.

  • Team Explorer 2012
    <RegistrySearch Id="TeamExplorer11Registry" Root="HKLM" Key="SOFTWARE\Microsoft\VisualStudio\11.0\InstalledProducts\Team System Tools for Developers" Name="Package" Type="raw" />
  • Team Explorer 2010
    <RegistrySearch Id="TeamExplorer10Registry" Root="HKLM" Key="SOFTWARE\Microsoft\VisualStudio\10.0\InstalledProducts\Team Explorer" Name="Package" Type="raw" />
  • Team Explorer 2008
    <RegistrySearch Id="TeamExplorer9Registry" Root="HKLM" Key="SOFTWARE\Microsoft\VisualStudio\9.0\InstalledProducts\Team Explorer" Name="Package" Type="raw" />

Workarounds

  1. Install Visual Studio Ultimate 2012 and Team Explorer 2012.
    -or-
  2. Add the highlighted registry key iff you have installed Team Explorer.
  3. Restart the TFS Integration Tools installation.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

    1: Windows Registry Editor Version 5.00
    2:  
    3: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\11.0\InstalledProducts\Team System Tools for Developers]
    4: @="#101"
    5: "LogoID"="#100"
    6: "Package"="{97d9322b-672f-42ab-b3cb-ca27aaedf09d}"
    7: "ProductDetails"="#102"
    8: "UseVsProductID"=dword:00000001

Special thanks to the ALM Rangers Martin Hinshelwood for reporting the issue and Vlatko Ivanovski for testing the registry key workaround.