Team Foundation Server 2012 Update 4 Object Model Installer

Microsoft Free

This is the stand-alone Object Model Installer for TFS 2012 (Update 4). This may be used for developing applications that integrate with TFS 2012.

Microsoft
(0) Review
Visual Studio
2012
Download (5,420)
12/3/2013
2012
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews
Q and A (7)
Sign in to write a review

Be the first to write a review.

Sign in to start a discussion


  • 64-bit
    2 Posts | Last post April 29, 2014
    • Does the 2012 object model *still* not support 64-bit processes, or are there supposed to be MSIL DLLS that work in 64 bit properly or 64-bit native DLLS that should be installed by this?
      
      I ask because the TeamFoundation Service clearly runs in Azure (given that it was taken down by the cert issue a couple weeks ago), and Azure services are 64 bit, so somehow they're able to access TFS. As of yet, I can't manage to get code to work in either the compute emulator or a service deployment because there seems to be at least some TFS DLLs that are only 32-bit. 
    • +1. I have been unsuccessful in finding a TFS 64-bit object model. My code runs against both Azure and TFS; Azure dlls are 64-bit, TFS dlls are 32-bit. As you can see, that doesn't work when you need to reference them in the same project.
  • Object Model Installer will not install on Clean machine
    1 Posts | Last post April 07, 2014
    • Hi, I have tried to install object model installer on a clean windows 7 64 bit virtual machine without any other software installed. it pops up a dialog ask me to install vc_runtimeMinimum_x86 and its dependencies after I specified the path manually. it appeared to installed with Error in the error log . How do I get it work automatically without specifying the path?
      
      Thanks
      
      one of the Error from the log 
      138C:0DD4][2014-04-07T11:31:16]: Error 0x80072efd: Failed to download BITS job.
      [138C:0DD4][2014-04-07T11:31:16]: Error 0x80072efd: Failed attempt to download URL: 'bits://go.microsoft.com/fwlink/?LinkId=325699&clcid=0x409' to: 'C:\Users\gg\AppData\Local\Temp\{cfaceae5-7bbe-48b2-a445-ef19cb34411c}\cab2F68B91AFC829BC46600063661E3ABBF'
      [
  • Does not include two worfklow related assemblies
    1 Posts | Last post December 09, 2013
    • This package does not appear to contain either of these assemblies:
      
        * Microsoft.TeamFoundation.Build.Workflow
        * Microsoft.TeamFoundation.Deployment.Workflow
      
      This seems to make working with 2012 builds impossible. We're on our way to 2013, but in the interim it would be wonderful if I could work on my 2012 based builds in VS2013.
      
      Any chance of getting these added?
  • Will not install on Windows 8 (8.1)
    3 Posts | Last post December 09, 2013
    • Trying to install this since I only have VS2013 installed and need to work on some Team Builds that are still 2012 based, but will not install because it complains that Compatibility Mode is enabled, but it is not.
      
      From the setup log:
      
      [1BE4:1E9C][2013-11-07T15:56:23]: MUX:  Stop Block: CompatibilityMode : Windows Program Compatibility mode is on. Turn it off and then try Setup again.
      
      Actually running under compatibility mode (for Win7 or Win8) does not work either, but I suppose that makes sense.
      
      Please update the installer so it works on Win8.1.
      
    • Hi Drew - We don't support installation of the 2012 OM on Windows 8.1.  We will release an updated OM soon (both for 2012 and 2013) that will unblock this.
    • Looks like this was released as part of Update 4. Thank you very much!
  • Adding an Installation Requirement for deployment?
    2 Posts | Last post November 08, 2013
    • I am trying to add an installation requirement using InstallShield LE.  There does not seem to be a unique way to check if Team Foundation Server 2012 Update 1 Object Model has been installed or not.
      
      Is anybody aware of a way to determine if any of the following methods can be used to determine if it is installed or not and what values should be used?
      
      •File path, by searching folders
      •Folder path, by searching all drives
      •Folder path, by searching in a specific folder
      •Folder path, by searching for a specific file
      •File path, as specified by a registry entry
      •Folder path, as specified by a registry entry
      •Registry entry
      •File path, as specified by an .ini file value
      •Folder path, as specified by an .ini file value
      •.ini file value
      
    • Hi MDUPRE - 
      
      To detect the TFS OM, look in the registry for the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\tfs\Servicing\11.0\objectmodelcore, with DWORD value "Install" set to 0x01.  You can find more info at http://blogs.msdn.com/b/heaths/archive/2012/08/03/detection-keys-for-visual-studio-2012.aspx, however, there is one difference.  The TFS OM only writes the keys to the 64 bit registry on 64 bit OSes (this is a bug we intend to fix in the future).
      
      Hope that helps,
      Andrea Scripa [MSFT]
  • Install on Windows XP Professional SP3
    2 Posts | Last post March 14, 2013
    • Erin,
      the previous 2010 standalone Client Object Model could be installed on a WinXP machine.
      It seems to be impossible with the new one (2012) :-(
      
      I' getting the message "The specified program requires a newer version of Windows"
      
      Is it going to be changed?
      
      Thanks!
      Elena
    • Found the same issue also for Windows 2008. In the log for the package the following entery can be found:
      
      Condition '(VersionNT >= v6.1)' evaluates to false.
      
      This means that only Windows 7 / 2008R2 and higher is supported.
  • Redistribution allowed?
    3 Posts | Last post January 06, 2013
    • Erin, the previous 2010 standalone Client Object Model was not allowed to be redistributed but I was wondering whether this has changed with this / the 2012 one?
      
      We do have CALs for all our users but deployment of some of our customization/tools was rather cumbersome due to this / installing a complete VS shell.
      
      Moreover, will these/the latest version by any chance be available via NuGet? Would help -a lot-.
      
      Thanks!
      -J
    • Hi J,
      
      The same rules apply to this release.  You cannot redistribute the object model, you can only link to it.  The end user will need to run the object model install and agree to the EULA.
      
      Thanks!
      Erin
    • Thanks Erin!
      
      -Jörg