Vault 4.1.1 Classic Client not registered with VS2003

jrogovsky · Post by **jrogovsky** » Wed Apr 23, 2008 10:07 pm

Hi,

I'm evaluating Vault as a replacement to VSS2005.

I have some .Net 1.1 projects that I have to maintain in VS2003. However, the Vault client does not seem to register with VS2003. It is registered (both "Classic" and "Enhanced" versions) with VS2005 and VS2008.

I've already tried the "Make Vault your default SCC Provider" trick mentioned in several other threads. I've also tried uninstalling and reinstalling.

My OS is Windows Server 2003 R2 Standard x64 with Service Pack 2.

Any ideas?

lbauer · Post by **lbauer** » Thu Apr 24, 2008 10:35 am

Check your registry settings under these keys -- what's listed there?

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceCodeControlProvider]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceCodeControlProvider\InstalledSCCProviders

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceGear]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceGear\SourceGear Vault Client]

Is sthis in your registry?

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceGear\Vault Client]
"InstallDir"="C:\\Program Files (x86)\\SourceGear\\Vault Client\\"
"SCCServerName"="SourceGear Vault Classic Client"
"SCCServerPath"="C:\\Program Files (x86)\\SourceGear\\Vault Client\\VS2003_Client\\VaultIDE.dll"

jrogovsky · Post by **jrogovsky** » Thu Apr 24, 2008 10:50 am

I don't know what happened but it seems to be working now.

This morning, when I opened an existing project in VS2003 it right away asked for my Vault credentials. I was able to unbind the project from VSS and rebind it to the copy I'd previously imported to Vault.

I'm not sure why this is suddenly working, I hadn't even rebooted since yesterday (when I was initially playing with installing the client).

Anyway, I'm happy. Thanks for a great product.

I checked the registry settings for keys you listed and they all contained references to Vault.

lbauer · Post by **lbauer** » Thu Apr 24, 2008 12:08 pm

Gremlins.