This package does not appear to contain either of these assemblies:
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?
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.
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
•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]
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?
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.
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.
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-.
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.