12 Mar 2015

3 Comments

Microsoft is committed to BOTH Git AND Team Foundation Version Control

In both the classroom while training and in the field while consulting over the past year I have heard all sorts of rumours about Microsoft moving away from Team Foundation Version Control (TFVC) over to Git. I have even had students in my class struggling with a change to Git and when asked why they were changing they answered “because Microsoft is moving away from TFVC”.  The incorrect assumptions that people have been making are often leading to incorrect choices when it comes to choosing a version control provider.

I do not have anything against Git or TFVC – they both offer great features to development teams. I simply ask that you choose based on which model works best for your team. Don’t make the choice based on rumours and hearsay.

Brian Harry, Technical Fellow at Microsoft, has written I blog post titled The Future of Team Foundation Version Control which I hope will be the final word on this. I hope so anyway.

  • Kate

    Hi Anthony

    I would like to believe your post but at #Build2015 today we saw one example after another of Microsoft abandoning TFS Source/Version Control for GitHub:

    Visual Studio Code only supports local Git repos yet no support for TFS Source/Version Control;

    Microsoft only referred to Github during Azure demos, no mention of TFS Source/Version Control whatsoever.

    Our company have recently heavily invested in TFS licences and MCSD ALM training for our devs, testers and BAs only for Microsoft to appear to be abandoning it for a new toy.

    Microsoft used to be an innovative leader but now one could might easily argue that they seem to be aimlessly following trends and abandoning their loyal business customer base that invest in their products.

    I await your response in earnest.
    Kate

    • Hi Kate,

      I agree with your observation that Git and Github were both mentioned often during sessions and keynotes at the Build conference today. I would not suggest though that this should be interpreted as “abandoning Team Foundation TFS Source/Version Control”. What should have been very clear during Build sessions today is that Microsoft are aggressively looking to get a much broader range of developers using Visual Studio or the new Visual Studio Code. Many of these developers (Linux/IOS platforms) are already using Git/GitHub so supporting that will be very important in attracting them. I wouldn’t be surprised to see an update in the future that expands version control option in Visual Studio Code to include TFVC.

      I am also not sure I understand your comment “… Microsoft to appear to be abandoning it for a new toy.” Microsoft are offering a CHOICE of version control provider. Your teams can choose between a centralised version control system (TFVC) or a distributed version control system (Git) depending on their specific needs or preferences. Your company’s investment in training across the entire Application Lifecycle Management (ALM) suite is sound in my opinion as ALM covers a much broader range of topics than just version control. For example Work Item Tracking, Requirements Management, Defect Management, Release Management and much more. I can’t really see Microsoft as “abandoning” anything here.

      Anyway, I hope you’re enjoying the Build conference.

      Cheers

      Anthony

      • Kate

        Hi Anthony,

        What you say makes absolute sense, especially regarding the MCSD ALM training, and I have to admit that your explanation is much more thorough and reassuring than the response I received via twitter (see @KimberlyKate101) from the Microsoft reps during Build2015. Much appreciated – thanx.

        xXx
        Kate