Vault 4.0.1.15780/VS 2005, VS2005 Source Control Provider

GENSI · Post by **GENSI** » Thu Jun 21, 2007 4:35 pm

I just updated to the latest client version and the Vault VS2005 Source control provider does not appear as an option under the plugin menu, only the VS2003 compatible version.

Do I need to do anything else to use the VS2005 provider?

Post by **jeremy_sg** » Fri Jun 22, 2007 7:27 am

What OS are you running? We've had reports of failing to register on Vista 64, but those should have been resolved with 4.0.1.

GENSI · Post by **GENSI** » Fri Jun 22, 2007 7:18 pm

Vista Business, 32-bit.

Post by **jeremy_sg** » Fri Jun 22, 2007 10:10 pm

Can you tell me if you see registry keys at:

HKEY_LOCALMACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0

or

HKEY_LOCALMACHINE\SOFTWARE\Microsoft\VisualStudio\8.0

GENSI · Post by **GENSI** » Tue Jun 26, 2007 9:12 am

There are keys in HKEY_LOCALMACHINE\SOFTWARE\Microsoft\VisualStudio\8.0, but no such node @ HKEY_LOCALMACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0.

Also, digging around in the registry, I see that there is a HKEY_LOCALMACHINE\SOFTWARE\SourceGear\ item with SCCServerName "SourceGear Vault VS2003 Compatible Client" and one for SCCServerPath which points to VS2003_Client\VaultIDE.dll path. No mention of VS2005, could this be the issue?

Post by **jeremy_sg** » Tue Jun 26, 2007 1:09 pm

Do you see anything in your vault_client_install.log file that might give clues as to why the 2005 client wasn't registered? You can find that log file in the %TEMP% directory of the user that installed the client.

GENSI · Post by **GENSI** » Tue Jun 26, 2007 2:56 pm

No, in fact I see no such log file, even when searching the entire local disk. I uninstalled the client, then reinstalled it (VaultClient_4_0_1_15780.msi) and still only the VS2003 Compatible client is listed. I see no version of VS2005 Vault client anywhere.

Post by **jeremy_sg** » Tue Jun 26, 2007 3:07 pm

Please email me using the button below this post. We need to figure out why the client custom actions aren't being run on your system.

Post by **jeremy_sg** » Fri Jun 29, 2007 7:38 am

GENSI got this correctly installed when he ran the client installer as the Vista administrator.