Question
I am using MSBuild to build my stuff. I want to use CruiseControl.net as by Build Server.
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.
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.
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)
Answer
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.
Interestingly, Jeremy Miller asked the exact opposite question on his blog last year.
< br > via < a class="StackLink" href=" http://stackoverflow.com/questions/1300/" >Is nAnt still supported and suitable for .net 3.5/VS2008?< /a>
0 comments:
Post a Comment