Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Source Safe / August 2005

Tip: Looking for answers? Try searching our database.

Q: Making VSS the Default Source Control Tool

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Richard J - 19 Aug 2005 16:05 GMT
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

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.