What’s New in Team Foundation Server 2010

A Lap Around

• Adam Cogan
• Chief Architect
• DEV204
• www.ssw.com.au
• Sydney User Group Convenor

Pain Points

• Better Merging
• Better Branching
• Better Project
• Better Scrum
• Better Build Server
• (already has) Better bug tracking = work items = linking requirements to code changes
• (not) Better integration with Project

Problems

1. How do you know where the project is at?
2. Why don’t developers do unit tests?
• Estimate
• Work
• Work
• Overtime
• Run out of time
3. MS Project is not used
4. SharePoint

Agenda

• TFS Admins
• PM
• Developers
• Testers

TFS Admins

• No VS 2005 Support – until RTM
• No test management publishing
• No office integration

The multi-tenanted Problem

• You want to share a TFS server with multiple companies
• You need complete isolation
• how do you do this in TFS2008?
• e.g. TFS Now

The solution – Team Collections in TFS2010

• Team projects can now be grouped into Team Collections
• Each collection has it’s own database

Database Changes

• TFS 2008 had 7 database
• TfsBuild
• TfsIntegration
• TfsVersionControl
• TfsWorkItemTracking
• TfsWorkItemTrackingAttachments
• TfsActivityLogging
• TfsWarehouse
• Now: A database per collection
• TFS_DefaultCollection
• TFS_<Collections>
• TFS_Warehouse
• TFS_Configuration

Gated Check-ins

• Can’t check in code that breaks the build
• Can’t override the policy!

Visual Branch Management

• Merging changes back into the trunk is a lot easier (visually drag a branch back into the trunk)
• Visually see which branches are in sync with the trunk