使用 NAnt 代替 MSBuild 有什么好处？
粗略地阅读这两个工具让我相信它们做了类似的事情：管理构建任务，这意味着它们执行支持获取源输入并最终生成可运行输出的操作。
从 .NET Framework 2.0 开始，MSBuild.exe 包含在框架中，无需 Visual Studio 即可调用。
NAnt 相对于 MSBuild 是否有优势，或者它们只是两个具有不同相关性的竞争工具？
Cursory reading about both tools leads me to believe they do similar things: manage build tasks which means they do operations that support taking source inputs and ultimately producing runnable outputs.
As of the .NET Framework 2.0 MSBuild.exe was included with the Framework and can be invoked without Visual Studio.
Are there benefits of NAnt over MSBuild, or are they just two competing tools that have different relevancy?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您可以使用 MSBuild 4.0（其中添加了属性函数和内联任务，最后在 NAnt 中可用但在 MSBuild 中不可用）- 无。 Microsoft 终于赶上了一个自 2007 年以来一直处于休眠状态的项目...之所以
创建 NAnt，是因为在 2001 年（第一个公开的 .Net beta）和 2005 年（MSBuild 第一个版本）之间，没有可用的官方构建工具。它填补了一个重要的空白，并且做得很好。然而，现在最好还是坚持使用 Microsoft 工具 - 您可以获得支持、Visual Studio 集成，甚至可以在 Mono 上运行。
If you can use MSBuild 4.0 (which added property functions and inline tasks, last things that were available in NAnt but not in MSBuild) - none. Microsoft has finally caught up to a project that has been dormant since 2007...
NAnt was created because, between 2001 (first public .Net beta) and 2005 (MSBuild first release), there was no official build tool available. It filled an important niche, and did it well. However, now it's probably best to stick to the Microsoft tool - you get support, Visual Studio integration, and it even runs on Mono.