Hey gang,
I'm drawing a serious blank on this one. I did this a few times in the
past, but it has completely slipped my mind now.
I had been asked to evaluate source control tools, other than SourceSafe.
I've done all that, with Visual Basic connecting to each of them in turn.
Now, I want Visual Basic 6.0 to connect back to VSS but cannot for the life
of me figure out where to do this at. If I simply turn off the Version
Manager tool (PVCS), VB tells me it cannot find VSS.
I thought I had clicked an option somewhere but, as stated, I am drawing a
huge blank on this one.
The odd thing is, I can still open the VSS Explorer and check files out/in
that way, but I cannot interface with VSS through any other means. Anyone
got any ideas?
Thanks.
Richard
Andrew McDonald - 20 Aug 2005 02:43 GMT
"Richard J" <RichardJ@discussions.microsoft.com> wrote...
> I'm drawing a serious blank on this one. I did this a few times in the
> past, but it has completely slipped my mind now.
[quoted text clipped - 13 lines]
> that way, but I cannot interface with VSS through any other means. Anyone
> got any ideas?
Look in the registry under HKLM\Software\SourceCodeControlProvider. A
'ProviderRegKey' entry in here contains a string describing the current SCC
provider. There's a list of the installed ones in the
'InstalledSCCProviders' subkey. The values seem to be the paths of subkeys
of HKLM, containing the actual metadata for the SCC provider. Setting the
provider value back to the SourceSafe path should bring the integration back
to it.
--
Andrew
Richard J - 22 Aug 2005 12:41 GMT
Thanks for the reply Andrew. That did the trick.
Richard
> Look in the registry under HKLM\Software\SourceCodeControlProvider. A
> 'ProviderRegKey' entry in here contains a string describing the current SCC
[quoted text clipped - 6 lines]
> --
> Andrew