[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: http://nidaros.homedns.org/subway/. 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.)