Home > .net 3.5, Microsoft, Visual Studio 2008 > Visual SourceSafe 2005 and Visual Studio 2008 – Fix

Visual SourceSafe 2005 and Visual Studio 2008 – Fix

November 20, 2007

After installing VSTS 2008 on my workstation and VSPro 2008 on our other development machine, I found a glitch with Visual SourceSafe 2005 that didn’t seem to exist in Beta 2.

After installing VSS on the machine, it doesn’t automatically set the Source Control mode to use Visual SourceSafe in Visual Studio 2008’s options.

To fix this, check the following:

Tools | Options

Under Source Control, change the “Current source control plug-in” from ‘None’ to ‘Microsoft Visual SourceSafe’.  Restart Visual Studio 2008 and the menus and functionality load as expected.

  1. Britt Bassett
    December 5, 2007 at 12:23 pm

    In the “Current source control plug-in:”, the only choice I have is “none”. Nothing else can be entered. I have been, and am still using Visual SourceSafe 6.0d on this computer.

    Do you know how to get VS2008 to find and use it?

    Thanks.

  2. December 5, 2007 at 12:35 pm

    @Britt-

    For Visual SourceSafe 6.0d to work on Visual Studio 2008, you’ll need to do a bit of manual labour at the command line.

    Make sure that Visual Studio is closed when you do this.

    Browse to your VSS6\win32 directory and run:

    “regsvr32 ssscc.dll”

    That should register the library and make VSS 6.0d available–at least that’s what my notes say; if I can find the original source of this, I’ll amend this comment.

  3. Britt Bassett
    December 8, 2007 at 2:30 pm

    Thanks, that did it for the older version. I decided to upgrade to the newer, VSS2005, and found this link which provided the latest info…

    http://blogs.msdn.com/richardb/

    VSS integration now seems to be working fine for me.

  4. March 23, 2008 at 8:19 pm

    Thanks for the tips mate, i’m searching for this.

  5. Manuel M
    August 5, 2008 at 7:30 am

    thanks for the tip, saved me a lot of time…

  6. Manoj
    February 5, 2009 at 6:06 am

    Thanks a lot Mr.David.
    Registering the dll worked.

  1. No trackbacks yet.
Comments are closed.
%d bloggers like this: