本文介绍了是南特仍然支持,适用于.NET 3.5 / VS2008?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用的MSBuild建立我的东西。我想用CruiseControl.net由生成服务器。

I am using MSBuild to build my stuff. I want to use CruiseControl.net as by Build Server.

现在,CCNET是指恶性很多,但看起来好像CCNET可以完成大部分的东西楠的可以做通过项目配置和MSBuild的。此外,南特似乎有点不支持的,与测试版几乎是一岁多了。

Now, CCNET refers nAnt a lot, but it looks as if ccnet can do most of the stuff nant could do through the project configuration and msbuild. Also, nAnt seems a bit unsupported, with a Beta release that is almost a year old now.

总之:我其实挺高兴的MSBuild(特别是因为它是官方编译器前端),有点不舒服恶性,但我不希望pmaturely判断$ P $

In short: I am actually quite happy with MSBuild (especially since it's the "official" compiler front end) and a bit uncomfortable with nAnt, but I do not want to judge prematurely.

什么是理由使用过南特的MSBuild?特别是随着CCNET,这似乎在功能方面重叠有点与恶性(和添加自动生成相关的东西)

What would be reasons to use nAnt over MSBuild? Especially with ccnet, which seems to overlap a bit with nant in terms of features (and adding the automated build related stuff)

推荐答案

如果你很高兴的MSBuild,然后我会坚持的MSBuild。这可能是由于这些情况下,您首先学习的工具是一个你会preFER之一。我开始与南特,可以不太习惯的MSBuild。我敢肯定,他们都将是相当一段时间。

If you are quite happy with MSBuild, then I would stick with MSBuild. This may be one of those cases where the tool you learn first is the one you will prefer. I started with NAnt and can't quite get used to MSBuild. I'm sure they will both be around for quite some time.

有两者之间有根本区别,可能是通过的之间的对话。

There are some fundamental differences between the two, probably best highlighted by this conversation between some NAnt fans and a Microsoftie.

有趣的是,杰里米米勒提出完全相反的问题<一href="http://$c$cbetter.com/blogs/jeremy.miller/archive/2007/09/20/is-there-a-good-reason-to-switch-to-msbuild.aspx"在他的博客去年相对=nofollow>。

Interestingly, Jeremy Miller asked the exact opposite question on his blog last year.

这篇关于是南特仍然支持,适用于.NET 3.5 / VS2008?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-23 07:13