.NET构建过程(.NET Build Process)

.NET构建过程(.NET Build Process)

我正在寻找在MS Based构建过程中使用的最好的免费工具集。 结帐，构建，打包，测试，部署等

我知道这个问题之前曾被问过，但它已经超过2年了，在我们的世界里是永恒的。

我希望开发一种易于适应类似项目的模式。 几乎像模板/饼干切割系统。

我目前正在研究使用CruiseControl，Powershell，MSBuild工具套件。

如果我们选择迁移到4.0，我们会遇到问题吗？ 还有更好的选择吗？ 限制？ 或者这些几乎可以满足我的需求。

我不喜欢的一件是包装过程。 实际上我们过去曾选择使用Visual Studio部署项目，但这些项目非常古老，我担心WIX对于实现它的人来说太复杂了。

All I am looking for the best free set of tools to be used in a MS Based build process. Checkout, Build, Package, Test, Deploy, etc.

I know this question has been asked before but it was over 2 years ago, and in our world that is an eternity.

I am looking to develop a pattern that is easily adapted to similar projects. Almost like a template/cookie cutter system.

I am currently looking into using CruiseControl, Powershell, MSBuild suite of tools.

If we choose to move to 4.0 will we have issues? Are there better alternatives? Limitations ? Or will these pretty much meet my needs.

One piece that i am never happy with is the process of packaging. We actually have opted in the past to just use Visual Studio Deployment Projects but those are very* ancient and my fear is WIX will be too complicated for the people implementing it.

最满意答案

我听说cruisecontrol.net很受欢迎，但我没有时间处理配置构建所需的XML文件。 我选择了teamcity， 如果你只有20个或更少的项目，这是免费的。 它很容易设置，因为它有vs2005和vs2008构建运行器，只需要构建解决方案文件。 我也有nunit，ncover和fxcop运行没有太多问题。 它适用于所有主要的VCS，但在某些情况下它不能自动标记（虽然SVN没问题）。 我不能评论自动部署，但我相信它可以做到。 它更好，因为这是我的列表中的下一个，我在选择持续集成解决方案时考虑过这一点。

I hear that cruisecontrol.net is popular, but I didn't have the time to deal with the XML files needed to configure the build. I opted for teamcity, which is free if you only have 20 projects or less. It is very easy to set up because it has vs2005 and vs2008 build runners that just need the solution file to build. I also got nunit, ncover, and fxcop running without too many problems. It works with all of the major VCSes, though in some cases it cannot label automatically (SVN is okay though). I cannot comment on auto deployment but I believe it can do it. It had better, because this is next on my list and I did think about this when choosing a continuous integration solution.