<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>BPoint - Latest Comments in NAnt - really?</title><link>http://brettveenstra.disqus.com/</link><description></description><atom:link href="https://brettveenstra.disqus.com/nant_really/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 18 Feb 2008 00:16:34 -0000</lastBuildDate><item><title>Re: NAnt - really?</title><link>http://brettveenstra.com/2007/10/09/nant-really/#comment-2152816</link><description>&lt;p&gt;I throw in my 2 cents here...I had a chance to use Ant in a Java project a  couple years ago, and I'd say if nNant is anything like it (and I think it's pretty similar), I'd say its worth using a script-based build tool for even the smallish projects, regardless of whether you're going the CI route or not.&lt;/p&gt;&lt;p&gt;I found Ant very simply once I was familiar with the tool...once you have a working knowledge of the tool, you can whip up a new build project in no time.  Then, you can do nightly builds minimally (and you're ready for CI when the time comes).  Plus, if you have a tool/script to bake the SVN  version number into the assemblies being built (very helpful come debugging-time), you can easily add that to your build process. And once you've got a build process in place, you'll definitely think of things to add to the build (testing, documentation, installer...)&lt;/p&gt;&lt;p&gt;I'd say it's work it, just for the nightly builds :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nathan Bedford</dc:creator><pubDate>Mon, 18 Feb 2008 00:16:34 -0000</pubDate></item></channel></rss>