On work item tracking, he says, “ We haven’t made use of this feature because we haven’t adapted our business process to it… which come to think of it doesn’t make sense.” You don’t have to use all the features of TFS.Ĭhoosing to use all of TFS touches the whole business of producing software. Michael’s company uses TFS for source control. If you prefer to stop at Ethan Allen and choose a coordinating set, that’s TFS. If you want to select each item of furniture separately, hunting through different stores until you find the best chair and couch and table for you, then git is your source control rug. Git doesn’t impose or supply any of these parts there are other solutions both open-source and commercial. It integrates all its parts, and then integrates with Visual Studio, Sharepoint, and Active Directory. TFS is a whole development workflow suite. What does this chart say? It says, “ Git does version control, and does it well” and “ TFS does version control and build automation and work item tracking and test tracking and analytics in a SQL Server data cube with graphs and charts.“ Below that, find discussion of the important feature differences, user experiences, and the one question that will tell you which is right for you. Here’s a high-level comparison of features, for those who enjoy such formats. Github has some of the same bells and whistles as TFS, but Github is outside the scope of this post. Second, do you want version control or a full suite including a build server, work item tracking, and analytics? git is version control only.
Why should your team use one or the other?įirst, if you don’t use Visual Studio, forget about TFS. Many features and versions are in process all the time.ĭevTeach attendees and speakers provided all the TFS information in this post. Development is distributed among thousands of contributors around the world. It was created to manage the source code of the Linux kernel, roughly 15 million lines of code.
Since not everyone lives in Redmond, TFS tries to minimize network traffic and keep the work on the server. TFS was designed big and bad-ass enough to support development of Visual Studio, like 5 million lines of code. TFS (Team Foundation Server) is Microsoft’s answer to version control. If you value developer freedom and individual work strategies, use git. TL DR: If you want an integrated, enforced process, use TFS.
0 kommentar(er)
