3. mariorod@microsoft.com @mariorod1

5. source control models

6. centralized OR distributed

8. centralized - scales to large code bases

9. distributed - best in class offline experience

10. Check-in Check-out

12. StrengthsBest for Check-in Check-out Scales to very large codebases Fine level permission control Allows usage monitoring Large integrated codebases Control and auditability over source code down to the file level

14. StrengthsBest for Check-in Check-out Scales to very large codebases Fine level permission control Allows usage monitoring Large integrated codebases Control and auditability over source code down to the file level Offline editing support Easy to edit files outside Visual Studio or Eclipse Medium-sized integrated codebases A balance of fine-grained control with reduced friction Full offline experience Complete repository with portable history Simplified branching model Modular codebases Integrating with open source Highly distributed teams

16. we need to embrace DVCS

17. Git OR Mercurial

23. Team Foundation Server / Service Project 2Project 1 3 rd Party Local Repo Other Remote Git Repo

27. User: …. TFS sucks Us: We are sorry... Why do you feel that way? User: Because [reasons] … is a centralized version control product Us: We are supporting Git User: I love TFS! Us: We love you too

28. Git (hosted by TFS)

29. decision at the project level

35. * Capability in preview – limits may apply. Authoring load tests requires Visual Studio Ultimate 2013 Preview. Version control (TFVC or Git) Comment on changesets & commits Work item tracking and tagging Team rooms Agile planning tools Feedback Management Agile Portfolio Management* Build* Web-based test case management* Load testing* New!