This post originated from an RSS feed registered with .NET Buzz by Korby Parnell. Original Post: 'Change Source Control' Menu Disappears in Visual Studio Feed Title: Korby Parnell Feed URL: /msdnerror.htm?aspxerrorpath=/korbyp/Rss.aspx Feed Description: Copyright 2003 Korby Parnell Fri, 01 Aug 2003 10:03:48 GMT ChrisAn's BlogX korbyp@microsoft.com korbyp@microsoft.com Alex Lowe Joins Microsoft http://blogs.gotdotnet.com/korbyp/permalink.aspx/536bb108-6a66-4dc6-8847-69f4d799bb55 http://blogs.gotdotnet.com/korbyp/permalink.aspx/536bb108-6a66-4dc6-8847-69f4d799bb55 Fri, 01 Aug 2003 10:03:48 GMT From ASP.NET MVP to Microsoft .NET Evangelist.  Success is the domain of good guys.  Welcome aboard Alex.  I look forward to meeting you in person.  Thanks to ScottW for posting the big announcement. Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho. Latest .NET Buzz Posts Latest .NET Buzz Posts by Korby Parnell Latest Posts From Korby Parnell

A reader recently emailed me the following issue/question:

"I recently installed the VS 2005 December CTP on a machine that also has VS 2003 installed. I uninstalled the CTP today and now my VS2003 'change source control' menu choice (from the file menu) has disappeared.

How do I get it back."

I've heard about this problem before and as I recall, this is a VSS-specific issue. However, it could affect other source control providers as well. This post explains how to regain the ability to change source control (unbind solution/project, rebind, disconnect/remove from source control, etc) The issue occurs under the following conditions:

1. You have Visual SourceSafe 6.0x and Visual Studio .NET 2002/2003 on your machine
2. You install Visual Studio Whidbey 2005 CTP or beta AND you install Visual SourceSafe 2005.
3. You uninstall VS2005 and/or SourceSafe2005.

Cause: SourceSafe 6.0x and SourceSafe 2005 cannot be installed side-by-side. When you install VSS 2005, it overwrites VSS 6.0x's registry settings.

To Fix: Re-register the integration dll (ssscc.dll) from the VSS 6.0x install, either by running regsvr32.exe (regsvr32 ssscc.dll) or by running ssint.exe provided with VSS6. If you're using VSS automation for FrontPage projects, you should also re-register the SSAPI.dll for IVSS interfaces.

I have not confirmed that these steps work as advertised so if the fix works (or does not work) for you, please drop a comment to let future readers know.