The lack of 64Bit TFS API DLLs is becoming a real pain for me. We have committed to a 64Bit server architecture for all our IIS and hence MOSS servers; both of these seem unable to WOW64 the 32bit TFS DLLs (though Cassini can!) so I cannot load any web front ends that use TFS such as eScrum or anything home grown on my main servers.
My only option is to run 32it servers as well for the primary systems. This is not too bad for IIS/ASP.NET bits, but it is not recommended to have a mixed 32/64bit frontend for MOSS.
I have to ask why is there no 64bit version of these TFS DLLs, what the hell do they do that is processor type related?
If my understanding is correct they are just a set of wrappers that make the TFS WebServices easier to use. The TFS WebServices are not designed for third party access and I was strongly warned off trying to use them by Martin Wooward at IMTC and he should know as he is part of the team that wrote the Java/Eclipse client for TFS. He said the webservices do not provided atomic functions, so the API does a lot of work to make sure you don’t corrupt the TFS system. However as it in the end the API uses the TFS WebServices it must just be making SOAP calls so why can’t we have a 64Bit set of DLLs?
So is this a problem for just me? Has anyone else got interesting workarounds?