Team Foundation Version Control Life after SourceSafe

1
Team Foundation Version Control Life after
SourceSafe

• Chris Menegay
• Notion Solutions, Inc.

2
INETAThe Face of .NET

• World-wide association of .NET User Groups
• 860 groups world-wide
• Over 810,000 developers
• Started and run by .NET User Group leaders
• Sponsors and supports both .NET and other
  professional user groups all around the world
• Sponsors
• Microsoft and MSDN
• New sponsors welcome!
• North America (NORAM) INETA Speaker Bureau
  consists of 57 world-renowned speakers
• www.ineta.org

3
New From The Ground Up
Visual Studio 2005

• Scalability
• Three Tier Architecture
• SQL Server 2005
• 500 Person Team
• Storage limited to SQL Server and hardware
• Reliability
• Atomic Check-ins
• Security
• Remote Development
• HTTP Transport
• Proxy Server

SOAP / HTTP(S)
MSSQL/TCP
SQL Server 2005
4
Parallel Development

• Multiple Releases
• Branching
• Create a copy of a set of files for a separate
  work effort (i.e. a release that will need to be
  supported)
• Each branch can have different permissions
  configuration
• Merging
• Combine the changes in one branch into another
  branch
• Multiple Checkouts
• File can be checked out by multiple developers
• Later combine the changes locally, before
  checking in

5
TFVC Concepts

• Changesets
• Workspaces
• Branch And Merge
• Shelving
• Locking
• Labels

6
Changesets

• Logical container of data related to check-in
• File and branch information
• Links to work items
• Check-in notes
• Comment
• Policy compliance
• Metadata (date, time, user)
• Unit of atomic checkin
• Uniquely identified
• Numeric identifier
• Incremental
• Represents a point in time of source repository

7
Workspaces

• Client side copy of source checked out from
  repository
• Owned by one user on one machine
• Changes in workspace create pending changes
• Typical Sequence of Events
• Check Out
• Coding
• Get Latest
• Coding, Testing
• Check-in
• Workspace Mapping Repository folder mapped to
  Local Folder

8
Branch And Merge

• Purpose
• Independent path of development (i.e. when a
  version or code base will need to be supported)
• Experimental development, keep or throw away
• Multiple development efforts to the same
  sub-system
• Branch
• A branch relationship is created in TFS to avoid
  duplication of history and metadata
• Path-space branching
• Intelligent copies (Copy on first write)
• Merge
• Sync a branch into another
• Cherry Picking changesets (include or omit)
• History can be queried
• Ability to show changes that have not been merged

9
Shelving

• Set aside pending changes without checkin
• Optionally revert to unmodified files
• Restore shelved changes by unshelving
• Unshelve other users changes
• Power of task branching with less overhead

10
Locking

• Applied to a file or folder
• Checkout Lock
• Prevents other contributors from checking out a
  branch or file
• More restrictive
• Check-in Lock
• Allows checkout, but not check-in
• Allows others to work with a file, but not check
  in
• One lock allowed per file or folder

11
Labels

• Label
• Is a selection of files from different branches
• Is an unversioned entity
• Includes a single version of any selected file
• Example
• Milestone
• like Beta2
• Use files from B2Release branch
• Omit XYZ.cs from branch
• Include XYZ.cs from B2QuickFix branch

12
Integrated Check-in

• Atomic
• A changeset is guaranteed to have all changes
  from a check-in
• Integrated
• Check-in policy applied (but override-able)
• Work Items associated
• Builds associated with Work Items
• Check-in notes
• All related to changeset
• Pending Check-in Window
• Notification possibilities
• Check-in Policy
• Can enforce tracking, Unit Testing, Static
  Analysis
• Customizable, extensible

13
Supporting the EnterpriseDistributed Development

• Designed for the Internet
• Web-based protocols HTTP HTTPS
• Optimized for high-latency, low-bandwidth
  scenarios

Caching proxy File content cached on LAN Ideal
for regional offices
14
Supporting the EnterpriseSource Control Proxy
SOAP Messages
File Transfers
SOAP Messages
File Transfers
SOAP Messages
File Transfers
15
Supporting the EnterpriseSource Control Proxy
SOAP Messages
File Uploads
SOAP Messages
Downloads
File Uploads
SOAP Messages
File Uploads
16
Clients

• Visual Studio 2005
• Team Source Explorer
• Team Source Command Line Utility
• MSSCCI Clients
• Visual Basic 6.0
• Visual Studio .NET 2003
• Others
• Third Party Tools
• Teamprise
• Unix, Linux, Mac OS clients
• Eclipse/Websphere integration

17
VSS Feature Differences

• VSS does not have
• Workspaces
• Changesets
• Shelvesets
• Content Merge, Namespace Merge (branch)
• Auditing
• Locking
• Atomic checkins
• Team Foundation Version Control does not have
• Share (but has much better support for parallel
  development)
• Pin
• Archive and Restore
• Destroy
• Branching and merging is a lot more reliable in
  TFVC
• Archive before migrating from VSS to TFVC!

18
Converters to TFVC

• VSS
• Pick and Choose folders
• Replays VSS actions to VSTS for history capture
• Reports
• Pre-migration analysis
• User mapping file
• Post-migration results
• Allows for pinned files
• Also see related Walkthroughs