Sneak Peak: Team System’s New Source Control Explorer


Hot off the presses, here's a grab of the new Source Control Explorer tool window in Visual Studio 2005 Team System, aka Whidbey. I'll provide a detailed description of each and every ui element in a follow up post next week. Dimmed folders and files are those that have not been retrieved into the current workspace (VSE1118) using the Get or Get Latest Version command.

I'm very proud to have contributed to the design of this tool window, which will be available for Beta developers in the next Community Tech Preview of Visual Studio 2005 Team System.

Comments (10)

  1. Rob says:

    When is the next Community Preview

  2. My ISV is determined to keep my life interesting. I’m aware of this issue and expect a resolution sometime soon.

  3. Paul M says:

    it just looks cool — by-bye VSS, hello Team System

  4. Mark Levison says:

    Could you comment on what Team System Scource Control will offer subversion?? We’re considering moving to subversion in the next few weeks and are wondering if its worth waiting for team system.

    As I mentioned in <a href="http://dotnetjunkies.com/WebLog/mlevison/archive/2004/05/10/13215.aspx">"SourceSafe Integration with VS .NET is evil"</a> – integration with VS .NET isn’t non issue.

  5. Whereas Subversion and VSS are different types of apples, Team Foundation is an orange tree. They just don’t compare.

    Like you, I’ve heard some good things about Subversion but I haven’t used it myself. So I can’t answer your question on a feature by feature basis.

    Here’s what I do know:

    1) Whereas we are planning to ship various source control migration tools (YourApp2TeamSystem) in the box, Subversion2TeamFoundation is DEFINITELY not one of them.

    2) Subversion is a standalone source control app, by design. Team Foundation is a software development system for teams in which source control functionality is exposed as a seamless part of the development process. Imagine being able to create a native link between a bug, requirement, TODO, or other work item and a version of your source control repository, a build, or an arbitrary collection of files (a configuration) at any point in time. Imagine being able to progress the state of a bug from AssignedTo:Me to AssignedTo:Korby, simply by checking in a set of source file revisions. Imagine being able to open up a work item and synchronize your local working files to the way they were when the work item was closed: all in two clicks. Imagine being able to create and enforce custom Checkin rules such as MustPerformUnitTest. That’s Team Foundation.

    I guess I’d encourage you to pick up the Beta when it gets released and try out Team Foundation for yourself. If your team says wait, wait. Else, don’t wait. HTH,

    Korby

Skip to main content