4
Vote

TFS plugin does not work when running ccnet as a 64 bit process

description

I don't know exacly who owns the problem, but people will say that the "TFS plugin does not work" so here goes.
 
 
The TeamFoundation assemblies that the TFS Plug-in uses are marked as Win32 only. They will not load in a 64 bit process. The exception will say that Microsoft.TeamFundation.VersionControl.Client can not be loaded.
 
The workaround to to set the 32 bit flag on ccnet.exe/ccservice.exe like this:
 
corflags /32bit+ ccnet.exe
 
But it would be nice to atleast get a better errormessage so you know what is going on

file attachments

comments

BHofmann wrote Mar 4, 2008 at 5:09 PM

I'm having the same problem, but did not have corflags.exe on the server. I had to copy it from my Framework SDK folder (%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin).

Thank you very much for solving this for me.

wrote Mar 4, 2008 at 5:11 PM

BradWilson wrote Mar 4, 2008 at 8:50 PM

IMO, the right fix for this is to stop using the TFS libraries and instead talk directly to the TFS web service APIs. The source control APIs are not overly complicated. This would also allow you to mainline the TFS plugin into the CCnet builds since it won't rely on any 3rd party APIs.

bhehe1 wrote Oct 3, 2008 at 10:16 PM

Wow. I think this might have just solved my problem after a day long fight. I'm sort of embarrassed for the CC.NET team... Who ever works on that installed - they really should do a 'detect x64' routine and warn people about this simple fix... or better yet.... just go ahead and bundle the corflags.exe tool and do this as part of the install. Is there any reason someone wouldn't want to do this? At the minimum detection and bringing up a window of known issues related to x64 installation would have been helpful.

anilk wrote Oct 9, 2008 at 1:39 PM

Yes, thanks for the tip. A life saver!
-Krip

wrote Sep 15, 2009 at 4:38 PM

rhencke wrote Sep 15, 2009 at 4:39 PM

This saved me from a big headache! Thank you!

wrote Apr 28, 2010 at 8:14 PM

wrote Feb 14, 2013 at 3:47 AM