blocks|key|3805594|text|我目前的工作主要是使用OSS构建过程，并以Cruise+Control作为引擎，这很棒。我建议，如果你不知道为什么你需要TFS，它可能不值得你花这么多钱。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3805595|关于OSS的东西，您必须记住的是，该软件或者已经被Java团队使用多年，或者该软件是类似Java代码的端口。它是健壮的，并且适用于特定的目的。|3805596|微软不能发布OSS代码，这就是为什么他们必须重新实现许多开源的东西。所以，不，这是不必要的，并且已经有数百万个项目在该堆栈上发布。另一方面，TFS还提供了许多OSS堆栈无法(轻松)实现的优秀功能，例如与bug/功能跟踪软件的集成。|3805597|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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.

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 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.

blocks|key|3805662|text|我总是走OSS的道路，从来没有遇到过问题。我也强烈推荐将TeamCity用于您的CI解决方案。有一个免费的许可证，我认为它在配置和反馈方面比CC.NET出类拔萃。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3805663|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've always gone the OSS way and have never had a problem. I would also highly recommend TeamCity for your CI solution. There is a free licence and I think it blows CC.NET out of the water for ease of configuration and feedback.

blocks|key|3805673|text|我每天使用TFS已经有大约一年半的时间了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3805674|3805675|源码管理是稳定的|unordered-list-item|3805676|你不能轻易地断开连接。文件签出到server.|3805677|Auto-merge工作很好，除了有时它损坏了源文件(编码问题)。|3805678|TFS有一种迟钝的感觉！？尤其是测试管理器。托管代码？|3805679|在测试部分有各种愚蠢的bug，没有什么严重的问题。|3805680|测试运行启动时间太长(挂起)。|3805681|我偶尔会遇到SQL死锁！？|3805682|问题跟踪太糟糕了。你被迫在缓慢的集成对话框中工作，web仅显示。我建议将它与其他问题跟踪系统进行比较，比如JIRA|offset|length|3805683|Builds+works+ok。|3805684|3805685|entityMap|0|LINK|mutability|MUTABLE|url|http://www.atlassian.com/software/jira/^0|0|0|0|0|0|0|0|0|0|1H|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|18|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|19|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|1A|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|1B|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|1C|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|1D|8|@]|9|@]|A|$]]|$1|P|3|Q|5|E|7|1E|8|@]|9|@]|A|$]]|$1|R|3|S|5|E|7|1F|8|@]|9|@$T|1G|U|1H|1|1I]]|A|$]]|$1|V|3|W|5|E|7|1J|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

I've been a daily user of TFS for about 1.5 years now. 

<ul>
<li>Source control is stable</li>
<li>You can't easily work disconnected. File check out goes to the server.</li>
<li>Auto-merge works great, except sometimes it corrupts the source file (encoding problem).</li>
<li>TFS has a sluggish feel!? Especially the test manager. Managed code?</li>
<li>There are various silly bugs in the test part, nothing critical. </li>
<li>Test runs takes too long to start (pending).</li>
<li>I get SQL deadlocks once in a while!? </li>
<li>Issue tracking sucks imho. You are forced to work in the slow integrated dialogs, web is display only. I recommend comparing it with other issue tracking systems, like <a href="http://www.atlassian.com/software/jira/" rel="nofollow noreferrer">JIRA</a></li>
<li>Builds works ok.</li>
</ul>

blocks|key|5216033|text|如果您使用的是TFS，请确保安装了VSTS2008SP1。我看到的绝大多数发帖抱怨的人都在使用2005版本。2005是典型的“Microsoft1.0”综合症。后来的2个“版本”已经修复了很多问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5216034|2008年的Service+Pack不仅仅是一个bug修复--还添加了许多新功能。|5216035|至于选择vs+OSS+-有很多讨论(这里和其他地方)。它不是一个便宜的产品--但它在很多情况下都是最好的选择(对其他情况来说也是最糟糕的)。|5216036|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If you are using TFS make sure you install VSTS2008SP1. The vast majority of people I've seen posting complaints are using the 2005 version. 2005 is the classic "Microsoft 1.0" syndrome. There were a LOT of problems that have been fixed by the 2 later "versions".

The Service Pack for 2008 isn't just a bug fix - but added many new features.

As far as the choice vs OSS - there are a lot of discussion (here and elsewhere). It isn't a cheap product - but it is the best choice for a lot of scenarios (and the worst for others).

blocks|key|2960616|text|我们研究了TFS，但最终选择了Subversion+%2B+Trac+%2B+VisualSVN。我们现在不做CI，但我想我们会使用Cruisecontrol。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2960617|我开始在许多开源项目中使用Trac，它是一个很棒的工具。这实际上只是TFS功能的一部分，因此您必须做出决定--如果您使用所有功能，TFS可能会更好地将所有功能结合在一起。Trac是一个wiki/bug追踪器/源浏览器。一切都是链接的--当你在提交消息中输入WikiPage的名称或说"Fix+bug+#1234“时，只要你在Trac中看到该消息，链接就会转到正确的位置。它是帮助您完成工作的工具，但通常不会妨碍您的工作。|2960618|VisualSVN是TortoiseSVN+(+Subversion客户端)和VisualStudio之间的桥梁，极大地提高了生产力。他们有一个免费的试用，而且之后不是很贵(每个用户50美元)，但很值得。|2960619|Trac的一个可能的缺点是在Windows环境中，在IIS上工作是一件痛苦的事情。我已经安装了Trac很多次了，但我很快就对尝试让它正常工作感到沮丧。我最终在不同的IP上安装了Apache+(也可以使用不同的端口)，然后它就变得无缝了。|2960620|除了我的团队中的一个人(他有一点经验)，以前没有人使用过subversion。有一对夫妇使用了VSS，仅此而已。每个人都很怀疑，但我会说，几天之内他们都改变了信仰。在完全学习Trac并习惯了一切(再过几天)之后，每个人都被完全接受并喜欢上了它。|2960621|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

We looked at TFS, but ended up going with Subversion + Trac + VisualSVN. We don't do CI right now but Cruisecontrol would be what we'd use, I think. 

I started using Trac with numerous open-source projects, and it's a great. It's really only a portion of what TFS does, so you'll have to make a decision there -- if you use everything, TFS probably does a better job of tying it all together. Trac is a wiki/bug tracker/source browser. Everything is linked - when you type in the name of a WikiPage or say "Fix bug #1234" in a commit message, whenever you see that message in Trac the links go to the right places. It is tool that helps you do your job and but stays out of the way, generally. 

VisualSVN is a great bridge between TortoiseSVN (a Subversion client) and VisualStudio, and greatly improves productivity. They have a free trial, and it's not very expensive afterwards ($50/user), but well worthwhile.

One possible downside to Trac is in a Windows world, it is a pain to get working on IIS. I've installed Trac many times, but got frustrated quickly trying to get it working properly. I ended up installing Apache on a different IP (could also use different port) and then it was seamless. 

Except for one person on my team (who had a tiny bit of experience), no one had ever used subversion before. A couple had used VSS, and thats all. Everyone was pretty skeptical, but I'd say within a few days they were all converts. After fully learning Trac and getting used to everything (a few days more), everyone is totally sold and loves it.

blocks|key|2959756|text|我们公司成功地使用了CruiseControl/SVN/nAnt/JIRA组合。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2959757|TFS的交易障碍在于，它只对较大的公司来说是值得的。对于拥有30个或更少开发者的小型公司来说，这将是非常昂贵的，它们已经从上面的开源组合中获得了很大的好处。|2959758|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Our company uses the CruiseControl/SVN/nAnt/JIRA combination with great success.

The deal breaker with TFS is that it is only worth it for larger companies. It will be terribly expensive for smallish companies with 30 or less developers, which would already benefit greatly from the above open source combo.

blocks|key|2959909|text|Subversion+%2B+Cruisecontol.Net是一个很好的选择。SVN+is功能丰富、稳定、灵活。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2959910|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Subversion + Cruisecontol.Net is a good alternative.
SVN is is feature-rich, stable and flexible.

blocks|key|736787|text|与一套单独的操作系统工具相比，使用TFS的真正好处是集成了各种可用的信息流。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|736788|*创建需求并插入到TFS中|736789|*创建一组任务，将它们与需求联系起来，并将它们分配给各个开发人员|736790|*每个开发人员处理自己的任务和签入，将任务分配给签入的变更集|736791|*错误修复，在这种情况下，变更集将与错误修复请求协调，您也可以将错误修复映射到原始需求|736792|一旦这样做了，所有的信息都可以用来跟踪项目并对工作进行评估，例如，错误修复导致了多少更改，这是产生了更多错误或更改请求的需求，等等。|736793|所有这些信息在中型和大型组织中都非常有用，从我现在看到的情况来看，不可能(或非常困难)跟踪集成不同的操作系统工具。|736794|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

The real benefit of using TFS compared to a separate set of OS tool is the integration of the various flow of informations available.
 
* Create a requirement and insert into TFS 
* Create a set of task linking them to the requirement and assign them to the various developers 
* Each developer work on his task and checkin, assigning the task to the changeset checked in 
* A bug fix come in, also in this case the change set will be coordinated with the bug fix request and you can also map the bug fix to the original requirement
 
Once done this all the information can be used to track project and make evaluation about the work, like for example how many changes a bug fix caused, which are the requirement that has generated more bugs or change requests and so on.
 
All these informations are very useful in medium and large organizations and, from what I'm seeing now, are not possible (or very difficult) to track integrating different OS tools.

blocks|key|5216342|text|TFS堆栈远不止是源代码控制和CI/夜间构建设置。想想项目管理，bug报告，所有这些加起来就不仅仅是CruiseControl，SVN和NAnt了。仅仅是报告本身就可能值得投资。还要记住，如果你是MSDN订阅者/ISV金牌合作伙伴等，你可能会免费获得其中的一些……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5216343|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The TFS stack is far more than source control and a CI/nightly build setup. Think about project management, bug reports and it all adds up to something more than just CruiseControl, SVN and NAnt. Just the reports alone might be worth the investment. And also remember that if you're a MSDN subscriber/ISV gold partner/etc. you might get some of this for free...

blocks|key|733242|text|我最近才开始日复一日地使用TFS，并且来自以前的开源堆栈，我发现它相当缺乏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|733243|虽然所有bug和任务跟踪的集成是一个非常好的功能，但负面影响超过了它。|733244|就我个人而言，我使用下面的堆栈，它为我提供了我们需要做的一切，从持续集成到企业规模的自动化部署，成本只有一小部分：|733245|733246|Subversion|unordered-list-item|offset|length|733247|Hudson|733248|nCover|733249|nDepend|733250|Simian|733251|Jira|733252|Jira+&+Subversion+Integration|733253|733254|entityMap|0|LINK|mutability|MUTABLE|url|http://subversion.tigris.org/|1|http://hudson-ci.org/|2|http://www.ncover.com/|3|http://www.ndepend.com/|4|http://www.harukizaemon.com/simian/|5|http://www.google.com.au/url?sa=t&source=web&cd=1&ved=0CCwQFjAA&url=http://www.atlassian.com/software/jira/&rct=j&q=jira&ei=nPeUTe2KNoLBcauk9JwH&usg=AFQjCNGx2m653qgbdvjNB8XxITgsQAI6eg&cad=rja|6|https://studio.plugins.atlassian.com/wiki/display/SVN/Subversion%2BJIRA%2Bplugin^0|0|0|0|0|0|A|0|0|0|6|1|0|0|6|2|0|0|7|3|0|0|6|4|0|0|4|5|0|0|T|6|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1K|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|1M|8|@]|9|@$J|1N|K|1O|1|1P]]|A|$]]|$1|L|3|M|5|I|7|1Q|8|@]|9|@$J|1R|K|1S|1|1T]]|A|$]]|$1|N|3|O|5|I|7|1U|8|@]|9|@$J|1V|K|1W|1|1X]]|A|$]]|$1|P|3|Q|5|I|7|1Y|8|@]|9|@$J|1Z|K|20|1|21]]|A|$]]|$1|R|3|S|5|I|7|22|8|@]|9|@$J|23|K|24|1|25]]|A|$]]|$1|T|3|U|5|I|7|26|8|@]|9|@$J|27|K|28|1|29]]|A|$]]|$1|V|3|W|5|I|7|2A|8|@]|9|@$J|2B|K|2C|1|2D]]|A|$]]|$1|X|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|2F|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]|16|$5|11|12|13|A|$14|17]]|18|$5|11|12|13|A|$14|19]]|1A|$5|11|12|13|A|$14|1B]]|1C|$5|11|12|13|A|$14|1D]]|1E|$5|11|12|13|A|$14|1F]]|1G|$5|11|12|13|A|$14|1H]]]]

I've only recently starting working with TFS day to day, and having come from a previously open source stack I find it quite lacking.

While the integration of all the bug and task tracking is a really great feature, the negatives out weight it.

Personally I use the following stack which gives me everything that we need to do from continuous integration to automated deployments on an enterprise scale at a fraction of the cost:

<ul>
<li><a href="http://subversion.tigris.org/" rel="nofollow">Subversion</a></li>
<li><a href="http://hudson-ci.org/" rel="nofollow">Hudson</a></li>
<li><a href="http://www.ncover.com/" rel="nofollow">nCover</a></li>
<li><a href="http://www.ndepend.com/" rel="nofollow">nDepend</a></li>
<li><a href="http://www.harukizaemon.com/simian/" rel="nofollow">Simian</a></li>
<li><a href="http://www.google.com.au/url?sa=t&amp;source=web&amp;cd=1&amp;ved=0CCwQFjAA&amp;url=http://www.atlassian.com/software/jira/&amp;rct=j&amp;q=jira&amp;ei=nPeUTe2KNoLBcauk9JwH&amp;usg=AFQjCNGx2m653qgbdvjNB8XxITgsQAI6eg&amp;cad=rja" rel="nofollow">Jira</a></li>
<li><a href="https://studio.plugins.atlassian.com/wiki/display/SVN/Subversion+JIRA+plugin" rel="nofollow">Jira &amp; Subversion Integration</a></li>
</ul>

blocks|key|3805630|text|我已经看到了这两种方法的实际应用(尽管我是一名Java开发人员)。pick+and+mix方法的好处是你可以选择所有东西中最好的部分(例如，我会查看Hudson+for+CI+-它非常适合Java，也可以用在.Net上，有很多插件，而且使用起来非常简单)。缺点是你必须自己做所有的集成。然而，在Java世界中，这变得容易多了。另外，不要让别人告诉你支持的产品更好。在这个领域的许多OSS产品上，质量都很好，您可以从C免疫力中获得更好的支持，而不是等待供应商的支持合同(IBM，我正在看着您)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3805631|希望这能有所帮助。|3805632|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I've seen both in action (though I'm a Java developer). The upsides from a pick and mix approach is that you can choose the best bits for everything (e.g. I'd check out Hudson for CI - its excellent for Java, works for .Net too and has loads of plugins and is really simple to use). The downside is that you have to do all the integration yourself. However, this is getting a lot easier in the Java world. Also, don;t let folks tell you a supported product is better. On many OSS products in this space the quality is excellent and you get better support from the cimmunity rather than waiting for an answer from your vendor's support contract (IBM, I'm looking at you)

Hope this helps.

blocks|key|2959841|text|我强烈同意这一观点，即只有当您确切地知道您需要TFS的用途时，才值得使用TFS。基于开放源码的，廉价或免费的插件，如Visual+SVN和TestDriven.Net是如此之好，以至于与VS的集成已经是无缝的了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2959842|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would agree strongly with the point that it is only worth using TFS if you know exactly what you need it for. The OSS-based, cheap or free add-ins like Visual SVN and TestDriven.Net are so good that integration with VS is seamless already.

blocks|key|3805697|text|我想我应该提出一个可以持保留态度的新观点，因为我还没有尝试过它，但我计划在即将到来的项目中将Bitten用于CI。它运行在Trac%2BSVN之上，这两个伟大的工具我已经成功地在许多项目中使用过。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3805698|entityMap|0|LINK|mutability|MUTABLE|url|http://bitten.edgewall.org/^0|1A|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I thought I'd throw in a new perspective that can be taken with a grain of salt because I haven't tried it yet, but I plan on using <a href="http://bitten.edgewall.org/" rel="nofollow noreferrer">Bitten</a> for CI in an upcoming project. This runs atop Trac+SVN, both great tools that I've used for many projects successfully.

blocks|key|2960532|text|我们已经在这里逐步建立了一个开发堆栈，我们目前正在使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2960533|2960534|Subversion|unordered-list-item|2960535|CruiseControl|2960536|RedMine+(集成了错误跟踪和源代码控制，包括维基、基本项目管理等)。|2960537|2960538|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

We've built up a development stack gradually here, we're currently using:

<ul>
<li>Subversion</li>
<li>CruiseControl</li>
<li>RedMine (integrates bug tracking with source control and includes wiki, basic project management, etc).</li>
</ul>

blocks|key|736845|text|我认为TFS是值得的，因为上面的帖子提到了所有额外的功能。它的持续构建功能严重缺乏，所以我们使用CruiseControl.NET来增强这一部分，这是非常棒的。如果我们现在就选择TFS，唯一的原因是我们正在转向跨平台开发我们的产品。所以如果你有想过这一点，想想OSS吧。Subversion/Trac将是我最喜欢的组合，而CruiseCOntrol.NET仍然是主干。使用mono的CC.NET在Linux和Mac上运行良好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|736846|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think that the TFS is worth it for all the extra features mentioned in above posts. It's continuous builds functionality is seriously lacking though so we augment that part using CruiseControl.NET which is awesome. The only reason we would choose against TFS if we were to do it right now is that we are moving to cross platform development of our products. So if you have even thought about that, think OSS. Subversion/Trac would be my favorite combo that way with CruiseCOntrol.NET still being the backbone. CC.NET using mono works well on Linux and Mac.

blocks|key|2960916|text|TFS2010有一个TFS+Basic，它不需要任何费用(除了你的msdn订阅/visual+studio许可证之外)。每个VS许可证限制为1个，但您只需要为非VS用户提供额外的许可证|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2960917|仅VS2010中的UI自动化就使TFS成为拼凑开源解决方案的赢家|2960918|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

TFS2010 has a TFS Basic, which costs nothing (over and above your msdn subscription/visual studio licence). 
It is limited to 1 per VS licence, but you only need additional licences for non VS users

The UI Automation in VS2010 alone makes TFS a winner over cobbling together open source solutions

blocks|key|5216535|text|值得一提的是，广泛的to特性的最佳替代品不一定是开源软件，而是低预算的商业软件，比如用于代码质量和架构探索的NDepend，用于代码覆盖的NCover，用于嵌套在集成开发环境中的测试的TestDriven.NET……|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5216536|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ndepend.com/|1|http://www.ncover.com/|2|http://www.testdriven.net/^0|1I|7|0|1X|6|1|2K|E|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

It is worth mentionning that best alternative to a wide range of TFS features are not necessarily OSS, but low-budget commercial, like <a href="http://www.ndepend.com/" rel="nofollow noreferrer">NDepend</a> for code quality and architecture exploration, <a href="http://www.ncover.com/" rel="nofollow noreferrer">NCover</a> for code coverage, <a href="http://www.testdriven.net/" rel="nofollow noreferrer">TestDriven.NET</a> for testing nested in IDE ...

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?

TFS vs open source alternatives?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们目前正在为.NET开发设置一个源代码控制/构建/更多的服务器，我们正在考虑要么利用Team Foundation Server (这需要很多钱)，要么结合几个开源选项，比如SourceForge企业版/GForge和Subversion以及CruiseControl.net等等。有没有人走上了全面开放源码软件的道路，或者只有当你想要把它做好并尽快开始工作的时候，它才是TFS？

问TFS与开源替代方案？
EN

回答 17

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问TFS与开源替代方案？EN

回答 17

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问TFS与开源替代方案？
EN