SCC Plug-in Switcher for Visual Studio

[Update: The feature depicted in the bitmap below will not be available until the Beta 1 release of the next version of Visual Studio. KorbyParnell DateTime.Now(:)] 

One of the top customer complaints about source control integration in Visual Studio .NET 2002 and 2003 has been the difficulty of switching from one source control provider (aka plug-in) to another. For example, if you normally use Visual SourceSafe but one day install the GotDotNet source control provider to enlist in a GDN workspace like .Text or FlexWiki, the GDN provider becomes your default source control provider for Visual Studio. The next time you attempt to add a solution to source control, you discover that you cannot add it to a VSS database.  Argh.

To work around this issue (at least until the next release of Visual Studio) you can fiddle with your registry manually or you can do the smart thing and install a free, third-party SCC switcher.

Last July, I pointed to a couple of these nifty little utilities from a blog post and added, “If you get a chance to compare and contrast (or have written any other SCC tools!), please post your comments.“

Within minutes, a reader commented, “Well, since you are asking, I feel compelled to mention my own SourceSelector, available halfway down this page: That makes three! Perhaps MS should take the hint, and include such functionality in VS.“

Good idea. Compelling argument.  Done. 
(This feature will be available in Whidbey.)

Comments (17)

  1. Joe says:

    >Good idea. Compelling argument. Done.

    >This feature will be available in Whidbey.

    What I’d really like to see is the ability to have different SCC providers on a per-solution basis.

  2. d says:

    What I would >really< love to see is VS.NET smart enough to just "know" what SCC provider a project uses. At our company we are currently using four (yes 4!) different SCC providers, depending on how our clients want to work with us. Why should I even have to manually switch SCC providers?? VS.NET should just know the SCC provider a project needs and attempt to connect to it.

  3. d says:

    BTW, forgot to add that last time I heard .Text was being hosted in SourceGears public Vault server.

  4. >>VS.NET should just know the SCC provider a project needs and attempt to connect to it.

    Assuming you’ve already added a solution to source control, Visual Studio Whidbey will switch providers automatically on Open.

  5. >>I heard .Text was being hosted in SourceGears public Vault server.

    Doh! Shows how much I know.

    In general, how comfortable are people with the idea of a hosted source control service? Does the GotDotNet or Vault model work for you and your team? Personally, I’m using it for the first time in the context of FlexWiki (which IS on GotDotNet last I checked ;). In spite of the slow gets and checkins, it seems like a decent, no-cost solution for community projects. But what about vital team projects? Does the inherent insecurity of http make a hosted SCC service a no-go? Is performance a major issue, or a minor nuisance? Is it possible and/or feasible to build software commercially using one of the existing hosted services as your source control provider?

  6. Very many thanks for a good work. Nice and useful. Like it!

  7. Poll Pitt says:

    I am so [url=]lucky[/url] on having what I have! And good luck in yours [url=]search[/url].

    Just visit [url=]my site[/url].

  8. Thank you so much for this great post  about <a href=""”>" title="broker business loan">broker business loan</a> and [URL=]broker business loan[/URL]