I know all versions of VSS have many horror stories and I feel I will escape to a better source control mechanism someday but in the short term I am just trying to do a little cleanup and would like your advice on this issue:
Objective – consolidate old VB6 source code in a "new" VSS 2005 database (currently all these old projects are checked in to an "old" VSS 6.0d database); eventually, eliminate the "old" VSS.
Progress so far – The new VSS 2005 database now contains a mixture of projects. Some are using Visual Studio 2008, some use Vstudio 2005, and the more recently added ones are the above mentioned VB6 projects. Individually all these projects and "solutions" come up OK, I can check in – check out, launch SourceSafe, view differences, etc.
But all the VB6 projects now in a VSS 2005 database launch VSS 6.0d when asked, rather than VSS 2005.
Is this normal and just something to cope with until I get to some better nonVSS approach? Or can VB6 be re-configured someway to launch VSS 2005 when I click Tools->SourceSafe->Run SourceSafe? I seem to recall VSS 6.0d got "integrated" into VB6 by way of the "Add-In Manager". At this point, the development PC with VB6 installed has both VSS 2005 and VSS 6.0d clients installed.
Best Answer
Going from memory, you need to try the following :
Look for a file in the folder where you have the SourceSafe client installed called ssint.exe. Copy this to where SourceSafe 2005 is installed, then run it. This should make Visual Studio load SourceSafe 2005 now. 2005 does not integrate with Visual Studio 6 as part of its installation. Update : http://social.msdn.microsoft.com/Forums/en-US/vbinterop/thread/86496254-2b17-4b7b-9134-00275fc4df77