Buck Hodges

Visual Studio Online, Team Foundation Server, MSDN

August, 2005

Posts
  • Buck Hodges

    Why doesn't Team Foundation get the latest version of a file on checkout?

    • 33 Comments

    I've seen this question come up a few times.  Doug Neumann, our PM, wrote a nice explanation in the Team Foundation forum (http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=70231).

    It turns out that this is by design, so let me explain the reasoning behind it.  When you perform a get operation to populate your workspace with a set of files, you are setting yourself up with a consistent snapshot from source control.  Typically, the configuration of source on your system represents a point in time snapshot of files from the repository that are known to work together, and therefore is buildable and testable.

    As a developer working in a workspace, you are isolated from the changes being made by other developers.  You control when you want to accept changes from other developers by performing a get operation as appropriate.  Ideally when you do this, you'll update the entire configuration of source, and not just one or two files.  Why?  Because changes in one file typically depend on corresponding changes to other files, and you need to ensure that you've still got a consistent snapshot of source that is buildable and testable.

    This is why the checkout operation doesn't perform a get latest on the files being checked out.  Updating that one file being checked out would violate the consistent snapshot philosophy and could result in a configuration of source that isn't buildable and testable.  As an alternative, Team Foundation forces users to perform the get latest operation at some point before they checkin their changes.  That's why if you attempt to checkin your changes, and you don't have the latest copy, you'll be prompted with the resolve conflicts dialog.

  • Buck Hodges

    Hold the shift key and double click

    • 3 Comments

    I've learned two shortcuts recently that I didn't know existed in TFS source control integration in VS.  These may or may not work based on the build you are using.

    Double clicking the Source Control node in the Team Explorer will bring up the Source Control Explorer window.  What I learned recently is that holding the shift key and double clicking Source Control will bring up the Pending Changes window.

    The other shortcut is more useful.  You may already know that double clicking a file in the checkin window will bring it up in the editor.  If you hold the shift key while double clicking a pending edit, it will launch your diff viewer so you can see what's changed.  That's kind of handy.

  • Buck Hodges

    Look for TFS Beta 3 in September, RTM in Q1 '06

    • 2 Comments

    Beta 3 for Team Foundation will be released in September along with Visual Studio 2005 Release Candidate 1.  One of the most significant points with beta 3 is that it will have a go-live license that includes data migration to RTM.  The details are in Soma's blog post for today: Visual Studio 2005 update.

    Here's a copy of the part that's TFS-specific.

    Simultaneously with Visual Studio 2005 RC1 [in September], we will also release Beta 3 of Visual Studio 2005 Team Foundation Server (TFS). TFS is Microsoft’s server-based product for team collaboration and is part of the Visual Studio 2005 wave of products. 

    TFS Beta 3 will include a Go Live license along with technical support for Premier customers, enabling organizations to begin deployment of their Team System collaboration tools immediately.  The Go Live license will also enable us to solicit an additional round of feedback from customers prior to shipping.  We have received fantastic feedback from customers, partners, and our own internal use so far.  Over the next several months, I want to encourage you to exercise TFS under your real-world conditions and send us feedback via the MSDN Product Feedback Center.

    At Visual Studio 2005 launch, we will continue supporting TFS Beta 3 with the rest of Visual Studio 2005.    Further, all data within TFS Beta 3 will migrate seamlessly and in-place to the final version of TFS.  We will ship TFS in the first quarter of 2006.

  • Buck Hodges

    Dogfood statistics update

    • 0 Comments

    John Lawrence posted the latest set of dogfood system statistics.  The deltas are from May I think, since it says checkins are up 4,500.  The June/early-July statistics are here.  One thing to note is that we now have more than 600,000 files and folders in the system.  Hopefully, we'll hit 1 million in the not too distant future.

    Note that you can get some of these same statistics for your own system, such as number of files and workspaces, using the QueryServerRequests web service call that I wrote about here.  Jeff Lucovsky recently wrote a post on command logging and tbl_Command.  You'll need that if you want to keep track of the number of gets issued, etc.

    Anyone want to take a guess on what day we'll hit the 10,000th changeset?  You can check out my changeset milestones post for some data.  We're at about 8,300 right now.

Page 1 of 1 (4 items)