使用Visual Studio 2013时，TFS和Git在源代码控制方面有什么重大区别？ [英] What are the big differences between TFS and Git for source control when using Visual Studio 2013?
问题描述
我使用Visual Studio 2013开始使用各种语言（C＃，C ++，PHP，Javascript，MySSQL）开展绿色牧场开发。未来，做一些iOS开发。我非常熟悉SVN，VSS和TFS的源代码控制。但是，我从来没有使用过Git。我更喜欢TFS进行流程管理/敏捷开发......这并不完美，但它很好地集成到Visual Studio中。
所以，帮助我在这两个系统之间做出决定。 ..使用Visual Studio 2013时，TFS和Git在源代码控制方面有什么大的区别？
- 在我的情况下，唯一的好处是本地存储库（并不是说它不重要）和iOS开发支持？
- 是Git命令行界面唯一的缺点（有些人会认为这不是一个缺点; -P）。
- 你有没有在Git的Visual Studio 2013 GUI中体验过？这足以支持没有命令行界面的基本分支/合并吗？
- 是否有详细的Git启动指南，显示Git与Visual Studio 2013一起使用？微软有一个视频，用于将现有的Git存储库集成到Visual Studio 2013中，但我正在寻找从Git和VS 2013起步的开始。
我不是在这里寻找一本书，而只是几个要点，也许是一些使用过TFS和Git的人的相关链接。
使用VS 2013时，TFS和Git在源代码控制方面有什么大不同？
MSDN的非常广泛的页面功能和不同之间的团队基础版本控制和Git 。
是我的情况下唯一的好处本地存储库（不说这是微不足道的）和IoS开发支持？
不，还有很多，但它们通常是Git的高级场景。本地回放，离线支持和完整的本地保真历史非常强大，您可以通过Visual Studio获得开箱即用的功能。还有一些其他功能也很棒！从一个存储库到另一个存储库的分支和合并功能非常强大。我建议您查看这些 Pro Git书。在TFS中的Git只是另一个git服务器，它几乎具有标准Git的所有功能。
在合并之前重写历史记录的功能允许您删除或合并一些较小的变更集，以便历史更清晰，更容易阅读为人。
Git命令的唯一缺点是（有些人会认为这不是一个缺点; -P）。
TFVC也有命令行，人们不会用它。对于那些想要使用Git的人而言，他们的功能永远不会超过TFVC，他们可能不会真的需要离开UI，但他们不会获得很多很酷的功能......
可能还有其他一些缺点，主要是由于它与人们习惯的不同。如果你没有花时间学习你做事情时做什么，那么在脚下开枪并不难。诸如Rebase和Squash等功能非常强大，并且创建了一个非常清晰的历史记录，但是如果使用不当，可能会导致人们无法再合并。 TFS有能力进行一些安全设置来剥夺制作权的权利愚蠢的决定在一个git仓库。
Windows上的Git用户非常酷的插件是 PoSHGit 。它在Powershell命令行中提供了命令自动完成功能。
你有没有在Git的VS 2013 GUI中体验过？这足以在没有命令行界面的情况下支持基本的分支/合并吗？
它拥有基本操作所需的全部功能。但是您需要能够将不同分支可视化，以了解发生了什么。由于Git服务器和本地回购只是Git，任何git客户端都可以在这里帮助你。 SourceTree是这里的一个选项。对于Windows客户端的Git是另一种。
对于标准操作，检入，检出，合并，分支（或推，拉，取，提交和合并）用户界面工作得很好。
有没有Git的详细启动指南，显示Git与VS 2013一起使用？ MS有一个视频，用于将现有的Git仓库整合到VS 2013中，但是我正在寻找从Git和VS 2013起步的开始？
从Git开始可以在很多地方找到...... 其他好消息： 还有一些值得安装的工具： There are tons of questions and answers about Git versus TFVC Source Control, but no current answers given the integration of Git into Team Foundation Server/Service that I can find. I'm starting green pasture development using a wide variety of languages (C#, C++, PHP, Javascript, MySSQL) using Visual Studio 2013. In the future, there will be some iOS development. I'm very familiar with SVN, VSS and TFS for source control. However, I have never used Git. I prefer TFS for process management/agile development... It's not perfect, but it integrates well into Visual Studio. So, to help me decide between these two systems... I am not looking for a book here, but just a few bullet points and maybe some relevant links from folks that have used both TFS and Git. What are the big differences between TFS and Git for source control when using VS 2013? MSDN has a very extensive page on all the features and differences between Team Foundation Version Control and Git. Is the only benefit in my case a local repository (not saying that's insignificant) and IoS development support? No, there's lot more, but they're often advanced scenario's of Git. Local Repo, offline support and full local fidelity on history is incredibly powerful, you get that out of the box with Visual Studio. There's a few other features that are great too! The ability to branch and merge from one repository to another is very powerful. I recommend you look up the Pro Git book for those. Git in TFS is just another git server, it has pretty much all features that the standard Git has. The ability to rewrite history before merging allows you to remove or combine a number of smaller change sets, so that the history is cleaner and easier to read as a human. Is the only drawback to Git the command line interface (some would argue that's not a drawback ;-P). TFVC has a command line too, people just don't use it. For people that want to use Git and never do much more than TFVC does, they probably won't really need to leave the UI, they won't get a lot of the cool features though... There might be a few other drawbacks, mostly due to the fact that it's different than what people are used to. It's not too hard to shoot yourself in the foot if you don't take the time to learn what git does when you do things. Things like Rebase and Squash are really powerful and create a very clean history, but it can leave people with the problem that they can't merge anymore if used incorrectly. TFS has the ability to put some security settings to take away the rights to make very stupid decisions on a git repository. A very cool add-on for Git users on Windows is PoSHGit. it provides command autocompletion on the Powershell commandline. Have you experienced in the VS 2013 GUI for Git? Is that enough to support basic branching/merging without the command line interface? It has all you need for basic operations. But you do need to be able to visualize the different branches to know what's going on. Since the Git server and local repo are just Git, any git client can help you out here. SourceTree is an option here. The Git for Windows client is another. For standard operations, check-in, check-out, merge, branch (or push, pull, fetch, commit, merge) the UI works just fine. Is there a detailed start-up guide for Git that shows Git being used with VS 2013? MS has a video for integrating an existing Git repo into VS 2013, but I'm looking for a start from scratch with Git and VS 2013? Starting with Git is available in a number of places... These are a few options: Other good reads: And a few tools worth installing: 这篇关于使用Visual Studio 2013时，TFS和Git在源代码控制方面有什么重大区别？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
What are the big differences between TFS and Git for source control when using Visual Studio 2013?
