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.