How do I get Vault 4.1.2 to work in VB6?

neal007 · Post by **neal007** » Tue Jul 22, 2008 2:00 pm

I have to go back and touch up some legacy apps and I'd like to get them in Vault. I'm running Vista x64 with VB6 Ent (SP6). In the Add-ins I do see Source Code Control loaded/running. How do I get Vault integration setup?

Thank you.

Beth · Post by **Beth** » Tue Jul 22, 2008 3:10 pm

I don't think we tested with VB6 on a 64-bit machine, so I'm unsure what to expect. Either way, start by closing VB6. Then open Vault, go to Tools - Options - General and select the box to make Vault your Default Source Control Provider. Then reopen VB6 and see if the option is there.

neal007 · Post by **neal007** » Tue Jul 22, 2008 3:19 pm

No, I tried/checked that from other search hits of the forum - no luck.

Beth · Post by **Beth** » Tue Jul 22, 2008 4:34 pm

Take a look at your vbaddin.ini file and perform the suggestion mentioned here: Enabling Source Control Functions in Visual Basic 6

neal007 · Post by **neal007** » Tue Jul 22, 2008 5:03 pm

Hi Beth,

That setting is simply to tell VB6 whether to start the Source Code Control Add-In which I stated was in fact loaded and started. I don't see anything regarding vault or how to integrate it. I only see the Tools...Source Safe menu.

Post by **jclausius** » Wed Jul 23, 2008 7:37 am

Neal:

If you're seeing "SourceSafe", it is most likely the Classic (MSSCCI) client's setting was over-written by a VSS installation.

Try this:
- Close down all Dev related apps (VB6, VS, DevStudio, etc.)
- Start up the Vault/Fortress client
- Tools -> Options -> General -> Uncheck the "Make Vault/Fortress your default SCC Provider". Click OK.
- Tools -> Options -> General -> Check "Make Vault/Fortress your default SCC Provider". Click OK.
- Close Vault
- Restart VB 6.

From the menu, does it say still say "SourceSafe" or does it now say "Vault" or "Fortress"?

neal007 · Post by **neal007** » Wed Jul 23, 2008 7:54 am

Hello Jeff,

I had tried that yesterday, did it again today, still just shows Tools...SourceSafe (see attached).

Post by **jclausius** » Wed Jul 23, 2008 9:06 am

Hmm...

Within HKLM\Software\Wow6432Node\SourceCodeControProvider\InstalledSCCProviders, do you see a string value for Vault or Fortress?

In the HKLM\Software\Wow6432Node\SourceCodeControProvider\ hive, what is the value for ProviderRegKey? Is it set to the Vault/Fortress' regsitry string value seen in the InstalledSCCProviders\ hive? Again, the value name is "ProviderRegKey" - this cannot be changed. Only the value's string can change.

Using the ProviderRegKey or InstalledSCCProvider string for Vault/Fortress, and accounting for the "Wow6432Node" variance to the string values for a registry re-direct, can you locate that registry hive?

And If you were to go to that registry node (again accounting for "Wow6432Node"), do you see entries for SCCServerName and SCCServerPath? Does the SCCServerPath point to a Vault_IDE.dll? And is that path valid?

neal007 · Post by **neal007** » Wed Jul 23, 2008 9:14 am

See attached. One other thing I did yesterday was uninstall/reinstall the Vault Client (4.1.2) in hopes it would pick up VB6 and add any info required, no change.

Post by **jclausius** » Wed Jul 23, 2008 12:28 pm

Try changing the ProviderRegKey to the value found under the InstaleldSCCProviders (which I believe is "SOFTWARE\SourceGear\Vault Client")

neal007 · Post by **neal007** » Wed Jul 23, 2008 12:38 pm

That did it! Thanks Jeff.

Post by **jclausius** » Wed Jul 23, 2008 12:56 pm

NP.

My guess is Vista x64 is restricting the Vault/Fortress client change the registry due to some permissions issue.

neal007 · Post by **neal007** » Wed Jul 23, 2008 12:58 pm

UAC is disabled, I'm logged in as Admin - not sure why that would be.

Post by **jclausius** » Wed Jul 23, 2008 1:03 pm

Whatever the case, we have a work-around modifying the registry.

I don't know what may be causing this, but I'll log a work item for someone to take a look at things.