Removing SourceSafe Integration from Visual Studio 6

Question

Recently, the integration of SourceSafe into a visual studio began to work poorly because we moved, and the SourceSafe server is located through a VPN, which goes through a slow connection. This made loading large projects in Visual C ++ 6 in 5+ minutes, because it had to talk to the "server" for each project. In addition, there are some errors that are dangerous in integration (automatic verification of some common projects will allow you to get the latest information about the wrong version of a forked file). This forced me to disable SourceSafe integration, however I did not find the menu option or the delete option. Google reported several registry changes, but none of them seemed to work.

Does anyone know how easy it is to remove the SourceSafe integration from Visual C ++ 6 without removing SourceSafe at all?

Answer 1

From http://support.microsoft.com/kb/236399 :

Source code management software such as Microsoft Visual SourceSafe, which integrates with the Visual C ++ Integrated Development Environment (IDE), can be configured to connect to the source code server during the Visual C ++ run. In such cases, the loss of a network connection will cause visual C ++ to start up very slowly. to improve performance, either ensure proper network connectivity or disable source code management software integration with the Visual C ++ IDE. To do the latter, close Visual C ++ and then use RegEdit.Exe to find the following registry key and set it to Disabled value before (DWORD) 0x00000001:

HKEY_CURRENT_USER\Software\Microsoft\DevStudio\6.0\Source Control\Disabled 

I followed this, and he seemed to be working on trying again. I think that maybe I had a second copy of the visual studio when I did this for the first time.

Answer 2

Open the .dsp and .dsw file in a text editor and delete the corresponding entries from the .dsp and .dsw file. Also, delete the .scc files.

Answer 3

The article provides information on how to do this.

The bottom line is that you must manually edit the .dsw and .dsp files in a text editor and delete several other files. See Article for more details.

Answer 4

If the solutions mentioned above do not allow you to do this:

Rename the folder: \ Program Files \ Microsoft \% vs% \ Common7 \ IDE \ VS SCC

VS will complain one day that the plugin will not be there, and you say yes to ignore it forever.

All files that have "received the latest", "read-only" and edited in VS will make VS complain and suggest "override", which is great for me.

What are you getting:

• Open VSS-related solutions quickly without matching VS content with the VSS server.

• Open VSS-related solutions and EDIT the files as you like, without clogging in the "check out" bs.

• This makes using a distributed source control system on top of a project tree with a VSS binding painless.

• The VSS client still works on its own just fine, including diff, checkout, checkin.

Answer 5

HKEY_CURRENT_USER \ Software \ Microsoft \ DevStudio \ 6.0 \ Source Control \ Disabled I followed this up and it seemed to be working on trying again. I think that maybe I had a second copy of the visual studio when I did this for the first time.

His work ..... Thanks Ajay

Answer 6

Which worked for us and is much simpler, does not require manual editing of the registry / file, and I'm sure it is safe:

1) Exit completely from Visual Studio.

2) Disconnect from the network (disconnect the cable and turn off the wireless network or disconnect the network adapters)

3) Open the VS6 workspace (DSW) for the project. When it starts, it will discover that it cannot connect to the VSS database that it wants and ask you about it ...

4) Tell VS to never try to reconnect to the original db control unit in the future.

5) Done ... VS makes all the changes to the THAT WORKSPACE / PROJECT setting for you. You do not disconnect VS from the source control at all (for example, editing the registry) and your files are not manually edited.