TFS与开源替代品? [英] TFS vs open source alternatives?

查看:353
本文介绍了TFS与开源替代品?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们目前正在为.NET开发设置源代码控制/构建/更多服务器,我们正在考虑利用Team Foundation Server(这需要花费很多钱)或将多个开源选项,例如SourceForge Enterprise/GForge和Subversion以及CruiseControl.net等.有没有人走过OSS繁忙的道路,还是只有当您想要正确解决并尽快开始工作时才使用TFS?

We're currently in the process of setting up a source control/build/and more-server for .NET development and we're thinking about either utilizing the Team Foundation Server (which costs a lot of dough) or combining several open source options, such as SourceForge Enterprise/GForge and Subversion and CruiseControl.net and so on. Has anyone walked down the full blown OSS road or is it TFS only if you want to get it right and get to work soon?

推荐答案

我的工作目前使用的主要是OSS构建过程,并以Cruise Control作为引擎,这很棒.我建议,如果您不知道为什么需要TFS,则可能不值得花这笔费用.

My work is currently using a mostly OSS build process with Cruise Control as the engine and it is great. I would suggest that if you don't know why you would need TFS, it's probably not worth the cost.

关于OSS,您需要牢记的一点是,该软件要么已经被Java团队使用了多年,要么该软件是类似Java代码的移植.它坚固耐用,适合特定用途.

The thing you have to keep in mind with the OSS stuff is that the software has either been in use by the Java crew for years previously, or the software is a port of similar Java code. It is robust and is suitable for purpose.

Microsoft无法发布OSS代码,这就是为什么他们必须重新实现许多开放源代码的原因.因此,没有,这是没有必要的,并且该堆栈上已交付了数百万个项目.不利的一面是,TFS还具有很多不错的功能,而OSS堆栈则无法(轻松)获得这些功能,例如与bug/功能跟踪软件的集成.

Microsoft cannot ship OSS code, which is why they have to re-implement a lot of Open Source stuff. So, no, it is not necessary, and there have been millions of projects shipped on that stack. The flip side is that there is also a lot of nice features that you get with TFS that you won't (easily) get with the OSS stack, such as integration with your bug/feature tracking software.

这篇关于TFS与开源替代品?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆