VB6 and VC++ 6.0 Integration on Windows 7

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear


Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear
PostPosted: Mon Mar 21, 2011 10:23 am
Vault 6 (and later) with Visual Basic 6 and Visual C++ 6.0 Integration on Windows 7

UPDATE
As of Vault 6, there is a new way to deal with getting programs to load the right .NET version for use with the Vault Classic Client. I will keep the old way of configuring VB6 or VC++ 6 posted below for those on older versions or as an alternative.

With Vault 6 or later:

1) Open your registry with admin privileges and go to HKLM\Software\(Wow6432Node\)SourceGear\Vault(Pro) Client\CLRVersions\

2) Create a string value. The name will be the full path to whatever binary EXE you are trying to integrate Vault. For example, it might be named "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" or "C:\Program Files\Microsoft Visual Studio\VB98\VB6.EXE".

3) Finally, for the value of the string, choose the version of .NET client that is installed on your system ( ie. "v2.0.50727" or "v4.0.30319" ).

4) In some cases you may need to modify the registry, under
HKEY_LOCAL_MACHINE\Software\Wow6432Node\SourceCodeControlProvider
add a string called ProviderRegKey and give it the data SOFTWARE\SourceGear\Vault Client.
Linda Bauer
SourceGear
Technical Support Manager

Posts: 8451
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
PostPosted: Thu Jun 05, 2014 10:25 am
Legacy Information

Typically, for VB6 and VC++ 6.0 integration with Vault 5 and earlier versions, your client machine needs the .NET Framework 1.1. However, this version of the Framework is not supported on Windows 7.
The workaround is to make VB6 load the .NET Framework 2.0 when starting VB6. For later operating systems, you can try having it load a later .NET framework that is on your system.

Here are the instructions for making VB6 load the 2.0 .NET framework:

1) Make a copy of the VaultGUIClient.exe.config (in the Vault GUI Client directory) and rename it "VB6.exe.config."

2) Copy the "VB6.exe.config" file into the same directory as the Visual Basic executable, "VB6.exe." Edit the VB6.exe.config file, adding runtime information after the <configuration> line

Code: Select all
<startup>
<supportedRuntime version="v2.0.50727"/>
<requiredRuntime version="v2.0.50727" safemode="true"/>
</startup>


so that the first part of the config file looks like this:

Code: Select all
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <startup>
    <supportedRuntime version="v2.0.50727"/>
    <requiredRuntime version="v2.0.50727" safemode="true"/>
  </startup>
  <system.net>


For Visual C++ 6.0, create an "MSDEV.exe.config" file using the instructions above and place it in the MSDEV.exe directory.

(Note: This is for VB6 and VC++ 6.0 in Visual Studio 6 only. No special configuration is needed for VB or Visual C++ integration in VS 2005/2008/2010.)

3) In the Vault Tools - Options - General, check the option 'Make Vault your default SCC Provider' and then click OK.

4) You may also need to modify your registry settings for Source Control Provider on the Vault Client machine. For 64-bit Windows 7:

4a) In the registry, under
HKEY_LOCAL_MACHINE\Software\Wow6432Node\SourceCodeControlProvider
add a string called ProviderRegKey and give it the data SOFTWARE\SourceGear\Vault Client.

4b) In the registry, under
HKEY_LOCAL_MACHINE\Software\Wow6432Node \SourceCodeControlProvider\InstalledSCCProviders,
change the key that might list the Vault VS 2003 Compatible Client to read as SourceGear
Vault Classic Client and give it the data of SOFTWARE\SourceGear\Vault Client
Beth Kieler
SourceGear Technical Support

Return to Knowledge Base (Vault)

Who is online

Users browsing this forum: No registered users and 2 guests

cron