How To: Switch Source Control Providers in VS.NET (Redux)


Following up on href="http://blogs.gotdotnet.com/korbyp/PermaLink.aspx/1f9c8c67-1269-4910-8608-edc917ea3f09">yesterday’s
post, here’s the manual procedure from the ever-helpful folks on the
Team Development team in  href="http://support.microsoft.com/default.aspx?scid=fh%3Ben-us%3Bvss&x=13&y=12">Microsoft
Product Support Services:


WARNING: If you use Registry Editor incorrectly, you may
cause serious problems that may require you to reinstall your operating system.
Microsoft cannot guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own risk.

To
change source control providers, follow these steps:



  1. Click Start, click Run, type
    regedit, and then click OK to open Registry
    Editor.
  2. In Registry Editor, expand the following registry key:
    class=indent>HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders


  3. In the right pane, double-click the registry key of the source control
    provider that you want to use (for example, Microsoft Visual
    SourceSafe
    ), and then copy the data of this key to the clipboard (for
    example, Software\Microsoft\SourceSafe).
  4. In the left pane, click SourceCodeControlProvider.
  5. In the right pane, double-click ProviderRegKey.
  6. In the Edit String dialog box, replace all of the text in
    the Value Data box with the contents of your clipboard, and
    then click OK.
  7. Close the registry editor.
  8. Restart your application for the changes to take
    effect.

This posting is
provided “AS IS” with no warranties, and confers no rights. Microsoft kann
für die Richtigkeit und Vollständigkeit der Inhalte in dieser Newsgroup keine
Haftung übernehmen.
Este mensaje se proporciona “como está” sin garantías
de ninguna clase, y no otorga ningún derecho.

Comments (11)

  1. jeff clausius says:

    korby:

    disclaimer: messing w/ your registry can be dangerous. don’t do it unless you’re not afraid you might hose your machine.

    if you are constantly switching b/w two different scc providers, a quick shortcut can be to export HKLMSoftwareSourceCodeControlProviderProviderRegKey when you have it set at one provider, and then export the key to a different reg file when set you have it set to another provider.

    a quick double click on the preferred .reg file, and a restart of vs.net, vs 6, etc. you should be up and running w/ the new scc provider.

  2. Tim says:

    This was an easy registry change. Worked like a charm

  3. vj~s says:

    This was really pretty simple and easy to follow process. Thanks a bunch:)

  4. Bob Rodes says:

    Copied directly from http://support.microsoft.com/default.aspx?scid=kb;en-us;319318. Suggest consulting this page in case Microsoft decides to change the rules.

    Bob

  5. kai says:

    if you have multiple source control providers (scp) installed (with vss 6c one of them but not the active) and then uninstall vss 6c, the registry will be left kind of corrupted with deleted entry SourceCodeControlProvider|ProviderRegKey.

    dot net studio will then complain:

    "The project <name of your project> appears to be under source control, but no source control provider is installed on this computer. Source control integration will be disabled for this project."

    though you still have installed other scp like sourcegear vault and/or perforce.

    you will have to manually re insert ProviderRegKey and restore your current active source control provider entry from (se above) InstalledSCCProviders.

  6. Dan says:

    just to add on the help …

    if you dont find ‘SourceCodeControlProvider’

    (ie

    HKEY_LOCAL_MACHINESOFTWARESourceCodeControlProviderInstalledSCCProviders

    )

    in the registry key, just register the VSSCC.dll by navigation to the VSS install folder

    regsvr32.exe vsscc.dll

    … move on after that …

  7. Jonathan Allen says:

    Thank you. You saved me a lot of trouble.