Well, I think that comes down to a cost/benefit analysis. If the benefits of building with NAnt outweigh the cost of learning, then your developers will likely hop on the bandwagon.
I phased it in at my workplace, where we do mostly web apps. Our devs use VS.NET for coding, testing, and debugging, and then use a NAnt script to publish the website. The NAnt script compiles the code as release, tags the source in subversion, and copies the content to the web server. That is a process that NAnt does a lot better than VS.NET, so everyone was more than happy to learn the new tricks. I'm not sure what NAnt would add to the initial code->test->debug cycle, as there are great tools to do unit testing in VS.NET. For awhile I was trying to put as much into the NAnt build as possible, doing unit tests and generating documentation, but then it took 4 minutes to run the script before I could test my code changes, so I ended up shelving that idea. Maybe when I have an oct-proc computer or something. Thanks, Ryan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anderson, Kelly Sent: Wednesday, October 19, 2005 12:39 PM To: nant-users@lists.sourceforge.net Subject: [Nant-users] Developers using NAnt Directly The developers on my team are used to working in the Microsoft IDE with sln and vcproj files. With NAnt, I have been able to use the <solution> task to compile code using this familiar environment. I don't want everyone on the team to be REQUIRED to learn NAnt to get their job done. So my thought is that the developers will do their programming and debugging in the traditional environment on their dev machines, and NAnt will be primarily used on the build machine. While this seems like a reasonable approach, it leaves me a little uneasy that there are essentially two processes going on here simultaneously, although one process is kind of a sub-process of the other. Does this bother anyone with more experience in these types of environments? Should I bite the bullet and require everyone to build with NAnt all the time? Is there any good reason to be that dictatorial (not that I have dictatorial powers)? (I know I can launch NAnt directly from the IDE, it's the process of adding files and changing settings that is more of an issue with the learning curve.) I'm also concerned that if I have NAnt on every dev machine, I've somewhat complicated the situation of setting up the dev environment, although I know I could solve that with NAnt as well. It's just more work to be done. -Kelly E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized. ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
