Translation The future of TFS Source control (Tfsvc vs. Git)

Description: Due to the limitations of the blog park, previously forwarded by the MVP Lu Jianhui article can not be placed on the homepage, but I will continue to forward, interested students please go to my blog home view.

Blog owner:

Translated from Microsoft Visual Studio ALM product Group boss Brian Harry's blog post the future of Team Foundation Server Version control.

The recent focus on Microsoft development tools must have a certain understanding of TFS, starting with version 2013, TFS provides 2 different ways of source control, Tfsvc and Git. With the massive popularity of git, it seems that tfsvc is becoming less important. In fact, far from this, in the blogger's own experience, although the Internet company, the entrepreneurial team is very fond of git, but for many traditional industries or large teams, the use of centralized tfsvc is still their first choice, there are certainly many such as security, control problems But the real situation cannot be ignored.

About Brian Harry.
Brian Harry is a member of Microsoft and is also the general manager of the team Foundation Server product group.

President

I've written about it before, but the problem is still lingering. Often people ask me, "Tfsvc is dead?" "And I think I must keep answering: No, no!"

We have added git support to TFS2013 because we feel that centralized (CVCS) source control and distributed (DVCS) source control are the most needed features in the industry. Our commitment to git is pretty big, because we have to provide the same functionality as TFSVC. There are, of course, some reasons for misunderstanding. We've talked a lot about git lately, very much. The industry is also very concerned about git, very much. And if you look at Microsoft's recent trends, you'll find that more and more teams within Microsoft are using Git. Many of my own teams have turned to git. These are facts, many people think we will abandon tfsvc, but we will not.

Most of our customers are still using TFSVC, and we take this very seriously. Tfsvc is still being used within Microsoft. Most of the newly created projects on Visual Studio Online (VSO) choose to use Tfsvc. There is no doubt that we have seen the trend toward git, and I also think that this trend will continue. In the next few years, I think git will use more than 50%, which is very likely. In any case, there are still hundreds of thousands of (nearly million) projects in use Tfsvc. Therefore, the tfsvc is still very important for a long time.

Well, the above are personal views, let's look at some facts:

The core of tfsvc is very mature and has a very large team in use tfsvc, it is very stable. We have recently paid more attention to the core features of Tfsvc, such as:

1. We have recently dramatically improved our web interface by adding features such as in-browser editing, check-in, and delete. These are all on the tfsvc.
2. We added a welcome page for Tfsvc, which is basically a wiki page based on tfsvc. (Blogger: wiki page using markdown language)
3. We support Tfsvc on Codelens, and some features are only available on tfsvc, such as the function of the branch change impact indicator.
4. The next generation of build systems Build.vnext support TFSVC.
5. The new Code search feature, although the preview version only supports git, but in the official release version will provide support for TFSVC.
6. Improvements to the code review feature, including multiple iterative reviews, web support, code review comment comments in Visual studio, and more. These all support tfsvc.
7. We have recently improved support for more than 260 characters on cross-platform team Explorer Everywhere (TEE) tools that support the MAC/LINUX environment, which is also on tfsvc. This is the problem of frequent spat in the community. (Blogger: Tee is a plug-in for eclipse that provides the ability to connect to TFS for Team development in Eclipse)
8. The renaming of the TFSVC project appears to be a small function, but the bottom floor makes a very big change.
9. We are developing support for the coexistence of 2 source code controls in the same project, which also requires modifications to the TFSVC.

Of course there's a lot I can't share with you right now. As you can see, tfsvc is not dead, and he is living well, we are still on this large-scale investment, and will continue to invest. For the user, you need to choose the most suitable way of working according to your actual situation, we will support you as always.

Hope this article can help you dispel doubts, if there is a problem, please contact me.

Brian

Please pay attention to this blog subscription number Anb-io. Push content Weekly, have the technology also has the life, with you to do a have the sentiment program ape.

Translation The future of TFS Source control (Tfsvc vs. Git)