Vault 3.5.2 or 4.0.0

[zumwalt]

When installining, checked off the box to integrate with VS.
Neither client version binds to VS.Net 2003 or VS 2005.
Is there a special registery setting that I need to change to make the binding happen?
Re-installing the client doesn't work.

[lbauer]

I could use some specifics --

What version of Vault Client are you using?

What version of Visual Studio?

When you say that neither client version binds to VS.Net 2003 or VS 2005, what steps are you following, and what, if any error messages are you getting?

[zumwalt]

Step 1) Install VS 2003
Step 2) Update Framework 1.1 to SP1
Step 3) Install VS 2005
Step 4) Update Framework 2.0
Step 5) Verify both load fine
Step 6) Install Source Safe Client 4.0, check box for use Vault as default for SourceSafe
Step 7) Open VS 2003, Check on SourceSafe settings, no choice for Vault, only Visual Source Safe
Step Create new project
Step 9) Change Source Safe Source, no choice for Vault
Step 10) repeat steps 7-9 for 2005, no choice for Vault
Step 11) Format the hard drive
Step 12) Install Windows XP Pro with SP2
Step 13) Repeat steps 1-5

Edit
Step 14+, format hard drive, repeat, each with only 1 version of VS, first 2003, format then 2005, test against 3.5.2 then 4.0
Step 14) replace Step 6 Client with 3.5.2
Step 15) Repeat steps 7-10, no Vault as Source Safe option

[lbauer]

For VS 2003-style (MSSCCI) integration with VS 2003 or VS 2005:
You need to check the box in Tools->Options->General->Make Vault my default SCC provider. This works for MSSCCI integration with either the Vault 3.5.2 or Vault 4.0 client.

In addition, if you're using Vault 3.5.2 with VS 2005, also go to VS 2005->Tools->Options->Source Control, choose Vault integration for the plugin.

In Vault 4.0, and VS 2005->Tools->Options->Source Control, choose VS 2003 integration for the plugin.

If that doesn't work, there may have been a problem updating the registry:

Vault Client needs to be listed under these registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders
HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Client

If you're using Vault 4.0, VS 2005 and the new VSIP (VS 2005) integration,

then those registry keys aren't relevant -- you should be able to just choose the VS 2005 integration:

VS 2005->Tools->Options->Source Control, choose VS 2005 integration for the plugin.

[zumwalt]

And thanks to the keys, here in was the problem:
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider

That only had sourcesafe, not the source gear.
I updated that key to say:
KEY: ProviderRegKey
Value: SOFTWARE\SourceGear\Vault Client

Now Vault shows up.
And it works like a charm. This is with VS 2003 and 4.0
thanks