SOS4.0 - VB6.0 IDE Intergration Problem.

FINDTARUN · Post by **FINDTARUN** » Mon May 31, 2004 11:56 pm

Hi,

I am on SOS Client Version 4.0 and have SOS Version 3.5.3 installed on the Server.
The code from the server is downloaded to a common server on the network, from where I copy the code to my machine.

The problem is that though I have SOS Client 4.0 installed on my machine, it does not pop up options to Check-In/Check-out, infact does not show any SOS options when I right click on a Form/Class in the Project Explorer window.

I confirm that the "Source Code Control" Add-in is loaded and check to load on Start-up as well.
Can someone please help me resolve this problem?

It might be beneficial to add the following points about my environment
OS - Win XP
VSS - 6. Installed.
SOS Client - 4.0
VB 6.0 with Service Pack 6

Looking ahead to a quick resolution.

Thanks,
Tarun.[color=brown][/color][color=darkred][/color]

Post by **jclausius** » Tue Jun 01, 2004 6:31 am

Tarun:

I'm not sure if this is the problem, but can you check out this thread related to vbaddin.ini?

http://support.sourcegear.com/viewtopic ... ht=vbaddin

Post by **jclausius** » Tue Jun 01, 2004 6:32 am

Also check to see if SOS is set to be the default Source Code Control (SCC) provider. I believe you can set this in the SOS options.

FINDTARUN · Post by **FINDTARUN** » Tue Jun 01, 2004 6:42 am

Thanks for the effort.

Unfortunately, I had already had a look at the link that you mentioned
1. Yes, the default Source Code Control is set in SOS
2. My vbaddin.ini does have the vbscc=3 enttry.

It still does not work. I hope that this can be solved.

Post by **jclausius** » Tue Jun 01, 2004 7:12 am

My vbaddin.ini does have the vbscc=3 enttry.

What if you set vbscc=1?

lbauer · Post by **lbauer** » Tue Jun 01, 2004 8:19 am

We've found that for VB 6 to integrate properly, you may need to install a copy of the Visual SourceSafe client on the SOS Client machine. The VSS client provides some element that VB 6 needs for integration.

Generally, if you have an SOS Client, you don't need VSS, but this is one situation where you do.

FINDTARUN · Post by **FINDTARUN** » Tue Jun 01, 2004 10:50 pm

Thanks Again for the help.

But if you please take note then I mention in my post:

- VSS 6.0 is installed
- VBADDIN.INI has an entry vbscc=3
I had already tried setting vbscc=1 but the result remains the same.

I am sure with your help we can solve this problem.

Regards,
Tarun.

lbauer · Post by **lbauer** » Wed Jun 02, 2004 1:57 am

Sorry, I missed the info about VSS already being installed.

Check these registry settings:

HKEY_LOCAL_MACHINE\Software\SourceCodeControlProvider

HKEY_LOCAL_MACHINE\Software\SourceCodeControlProvider\InstalledSCCProviders

What values are listed?

SourceCodeControlProvider\ProviderRegKey should be SourceOffSite.

InstalledSCCProviders should list both SourceSafe and SourceOffSite.

FINDTARUN · Post by **FINDTARUN** » Wed Jun 02, 2004 2:57 am

Hi,

----------------------------------------------------------------------------------
YOUR RESPONSE

"Check these registry settings:
HKEY_LOCAL_MACHINE\Software\SourceCodeControlProvider
HKEY_LOCAL_MACHINE\Software\SourceCodeControlProvider\InstalledSCCProviders

What values are listed?
SourceCodeControlProvider\ProviderRegKey should be SourceOffSite.
InstalledSCCProviders should list both SourceSafe and SourceOffSite."
----------------------------------------------------------------------------------

1. SourceCodeControlProvider\ProviderRegKey contains "Software\SourceOffSite\SourceOffSite"

2. InstalledSCCProviders lists "SourceOffSite" ONLY.
The only entry is "SourceGear SourceOffSite" with a value "Software\SourceOffSite\SourceOffSite".

And of course, HKEY_LOCAL_MACHINE\Software\ has an entry for SourceOffSite. The hierarchy is:

SourceOffSite\SourceOffSite\SCCServerName value "SourceOffSite"
SourceOffSite\SourceOffSite\SCCServerPath value "C:\Program Files\SourceOffSite\SosScc.dll"

I hope this should help us nail down the problem.

Waiting to get over this issue.
Appreciate your support.

Regards,
Tarun.

lbauer · Post by **lbauer** » Thu Jun 03, 2004 9:00 am

If VSS isn't listed in the registry as an SCC provider, then I'd suggest re-installing the VSS client. I would think that VSS needs to be recognized as an SCC provider in order to provide the necessary integration elements.

FINDTARUN · Post by **FINDTARUN** » Tue Jun 08, 2004 12:36 am

Thanks Again for your time.

I now have VSS reinstalled again and thus "InstalledSCCProviders" lists both SOS and VSS.
But, the integration still does not work.

Anything else that I should do?

Thanks in advance,
Tarun.

lbauer · Post by **lbauer** » Tue Jun 08, 2004 8:01 am

What's listed under this key:

HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider ?

FINDTARUN · Post by **FINDTARUN** » Tue Jun 08, 2004 9:55 pm

HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider has a key "ProviderRegKey" which has a value - "Software\Microsoft\SourceSafe"

Tarun

FINDTARUN · Post by **FINDTARUN** » Tue Jun 08, 2004 9:59 pm

Hi,

To reduce further shortage of information, I will put in my registry values here:

[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider]
"ProviderRegKey"="Software\\Microsoft\\SourceSafe"

[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders]
"SourceGear SourceOffSite"="Software\\SourceOffSite\\SourceOffSite"
"Microsoft Visual SourceSafe"="Software\\Microsoft\\SourceSafe"

[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\Options]

[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\Options\AddFilesToSccWhenAddedToHost]
@="2"

[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\Options\CheckinAllFilesOnCloseProject]
@="2"

[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\Options\CheckoutMakefileOnOpenProject]
@="0"

[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\Options\DeleteFilesFromSccOnRemoveFromVB]
@="2"

[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\Options\GetOnOpenProject]
@="2"

[HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\Options\ResultsDialogPosition]
@="27 48 392 223 "

I hope the picture should be clearer in order to fix the problem.

Waiting to have this solved,
Tarun.

lbauer · Post by **lbauer** » Fri Jun 11, 2004 7:50 am

This key determines your default SCC provider:

"ProviderRegKey"="Software\\Microsoft\\SourceSafe"

Right now it is SourceSafe. Try editing this to SourceOffSite and see if that helps:

ProviderRegKey=Software\SourceOffSite\SourceOffSite