Released: Visual Studio .NET SCC Plugin for gotdotnet Workspaces


As Peter Bromberg notes, we recently released an updated source control plug-in* for gotdotnet Workspaces that enables you to work on projects stored in gotdotnet (check in, check out, and other source control operations) from the comfort of your very own VS.NET 2005 (or 2003) IDE.



[Peter Bromberg]
Kudos to GotDotNet Team: VS.NET SCC Workspaces Provider and FIX for switching!


They’ve been making improvements over at gotdotnet.com, not the least of which is their new SCC plugin to use the GotDotNet Workspaces source control arrangement. Not only does it work very nicely in VS.NET 2005, it also works with VS.NET 2003!

It’s just like working in VSS; the only difference is that since you are working via WebServices, it’s a bit slower. But everything works! Really a boon to developers who like the Gotdotnet Workspaces concept and have small groups of developers who work together on a project.

The only downside is that when you want to get a project out of your regular VSS provider, IIT BREAKS and doesn’t work!

But there are several fixes, the best one I’ve found is Soenke Schau’s Sourcecode Control Switcher.

This little tray app tells you your current provider and let’s you switch at will by changing the Registry entries for you. And, you don’t need to leave it running. Just put a shortcut to the desktop and bring it up when you need it.”


I too like Soenke’s source control switcher. For other utilities that do the same thing, see How To: Switch Source Control Providers in VS.NET (ReduxRedux). I should also note that the ability to switch source control providers, say from VSS to Gotdotnet, is now baked into VS.NET. If you have more than one scc provider registered, you can now choose the one you want to use from the Source Control menu. Call me nostaligic, but I still prefer the systray utilities. Nevertheless, it’s good to have options.


—-
*If you have Visual Studio .NET 2005 installed, download this SCC plug-in. Once complete, open Visual Studio, click File, click Source Control, and then click Open from Source Control. If and when you need to switch from the Workspaces SCC provider to Visual SourceSafe, Team Foundation, Perforce, Clearcase, etc, open Visual Studio, click Tools, click Options, click Source Control, and then select Plug-in Selection. Select the SCC plug-in you wish to use instead of Workspaces, and then click Ok. The SCC provider is a solution-level setting. You cannot add one project in a solution to workspaces, for example, and another project in the same solution to Team Foundation.


If, for some odd reason, you should ever want to revert to using the winforms control to perform source control operations on the files in a gotdotnet Workspace, go to this page. I’ve created the workspace with which this URL is associated for this purpose so you may have to join the workspace to access the page. Don’t worry. Just do it.


If you have Visual Studio .NET 2003 installed, download this SCC plug-in. Once complete, open Visual Studio, click File, click Source Control, and then click Open from Source Control. You should see a dialog box that prompts you to log into gotdotnet. If and when you need to switch from the Workspaces SCC provider to Visual SourceSafe, Team Foundation, Perforce, Clearcase, etc, you must install and use one of the SCC switcher utilities that I point to in How To: Switch Source Control Providers in VS.NET (ReduxRedux) and related blog posts. It’s possible to flip a bit in the registry but that’s just soooo Raymond Chen.

Comments (8)

  1. MSDNArchive says:

    Now you just have to get the workspaces winforms/control thingy to work with the RTM of .NET 2.0. 🙂

  2. MSDNArchive says:

    Yyyyyeah. A work item has been created, triaged, and is in the queue for this issue.

  3. MSDNArchive says:

    I forgot to mention that the winforms 2.0 thingy works for me but I have reproducible reports from other users that it is broken for them. Thus, the fix may involve the publication of yet another complicated, gotdotnetesque workaround. Yuck.

  4. Andy Schroeder says:

    Does this work with express versions of VS.NET 2005? I was under the impression that plug-ins where not available in express versions, but I also heard that SCC source control would work. So can this be used with VS.NET express?

  5. Tyrone says:

    Has anyone thought about converting the Winforms control to a Windows appliction and deploying it via Click Once?

  6. Dale says:

    The old look and feel was better over all, but one specific area that I find frustrating is the user example section. The navigation is only on the top so after scrolling through a page of user examples, you have to scroll back up to the top to click for the next 25. That feature should, as it was in the old model, be on the bottom of the page as well.

    Other wise, thanks for a great service and site!

  7. MSDNArchive says: