This is what we do. Developers develop with Visual Studio, and the build automation happens with Nant on the server pulling code from source control. In fact, our developers don't really need to build locally at all (but they do anyway). They can launch a server-side Nant build from a custom web page (you could also accomplish this with CC.Net).
I can't see why you would need your developers to have Nant locally. This would require synchronizing the local and server Nant scripts. The only caveat to this situation is that any special steps needed to produce you build output locally would need to replicated in Nant scripts. Thankfully, that is exactly what Nant is good at, and you can make your server build far more powerful, integrating lots of disparate elements (like documentation, unit testing and distribution packages) that you could easily do locally. e -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anderson, Kelly Sent: October 19, 2005 12:39 PM To: nant-users@lists.sourceforge.net Subject: [Nant-users] Developers using NAnt Directly 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. ------------------------------------------------------- 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
