#1
|
|||
|
|||
Can't find Team Foundation Server exe
I've got two build machines, and one of them happily finds tf.exe for my Team Foundation Server step, but the other doesn't (same script):
Unable to auto-locate Team Foundation command-line executable; specify the full executable path + filename on the Options tab On the machine that succeeds to run the step, it outputs the following for the command it is calling... "c:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\tf.exe" And on the machine that if fails, tf.exe is in exactly the same folder. I checked my global macros, and DEVSTUDIO_NET_DIR is correct ("c:\Program Files\Microsoft Visual Studio 9.0") So how does VBPro auto-locate the exe and why is it not finding it? What am I missing on one machine but not the other? James |
#2
|
|||
|
|||
The Team Foundation action locates the path for tf.exe by looking for the registry value
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio \9.0\InstallDir (actually looking for various versions). Apparently, it is not finding that registry entry on the problem machine. |
#3
|
|||
|
|||
Any ideas why VisBuildPro wouldn't find that registry entry, because it's there in my build machine's registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio \9.0] "InstallDir"="C:\\Program Files\\Microsoft Visual Studio 9.0\\Common7\\IDE\\" and the "tf.exe" file exists in that folder. Indeed, if I enter the full path to the tf.exe file in the build item's Options tab, the step works fine. James |
#4
|
|||
|
|||
Which version of VBP are you running (Help | About | Install Info)?
|
#5
|
|||
|
|||
6.2a
I ran the same script on an eval of the 6.2a on another machine (my development machine) to see what happened, and that too fails to find the TF.exe, except this time gave a different error: Failed to create process: The system cannot find the file specified. Our build machine is a VMware image of Windows 2003 Server R2, and my development machine is XP SP2. James |
#6
|
|||
|
|||
v6.2a didn't support VS 2008; v6.7 does.
|
|
|