Hey all, Yep, and one of the things that irks me about vs.net is its placement of various temp directories. It always creates obj dirs in the most random places (and I can't get rid of them since it locks the files).
BTW. There is a VS.Net addin for doing pre/post build events that let you run programs or macros. But NAnt is much more than that. We also support things that VS.Net doesn't. But lets be clear. VS.Net is development environment, and not really a real build environment; tho it does build the current code you are working on. NAnt is a build environment, and not a development environment at all. The best option in my mind would be to use VS.Net as an editor( and you have more options than that), and NAnt to do the builds. The short of it is, can VS.Net copy files around your filesystem? Well, not really, but NAnt can. That doesn't make NAnt better, just more geared towards a build tool than VS.Net. But hey, take a look and see what you think. For very simple projects, where you are already using VS.Net, there is probably no reason to use NAnt. But if you don't have VS.Net, there are a whole lot of reason to use NAnt. And when your build gets more complicated, there are a whole lot of reasons to use a more full-featured build tool. Here are a few examples: ---) You want to build multiple versions/flavors of your product ---) You have a large number of inter-dependant projects (assemblies) to build. ---) You want to build multiple source language projects (like 2 vb.net, 2 managed c++, and hand-full of c#) and zip them up. ---) You need to build a signed and unsigned version together ---) You plan on scp'n them up to another server ---) You want some additional logic in your build process ---) You want to do unit testing before you call a build good. :) ---) You need to run a custom program to generate some of your code and you want to validate it first. ---) You need to download a file from the internet to do your build. ---) You lika da juice... I could go on... What are your favorite reasons to use NAnt? ----- Original Message ----- From: "Jeffrey McManus" <[EMAIL PROTECTED]> Subject: [Nant-users] Advantages of NAnt > Kishore, > > You're correct that you can build a complicated > project just fine in Visual Studio .NET. NAnt gives > you significant new capabilities at very little cost. > When you build using NAnt, you can: > > - Kick off calls to external processes (such as > email, the file system, or an automated unit testing > system like NUnit) > - Kick off your build from a centrally-managed > location (i.e., a server) so the "one true" version of > your build resides in one and only one location > - Build your software on any machine regardless of > the presence of Visual Studio .NET > > I'm sure that others could come up with additional > benefits but these are the main ones that impact me > today. > > -Jeffrey > From: Kishore Chaliparambil <[EMAIL PROTECTED]> > Can someone tell me what is the advantage of using > Nant to build the assemblies rather than using the > devenv.com using the he solution file. > > I can see that it is helpful if one does not have > Visual Studio.NET. But are there any other advantages. > > Any information will be helpful because We are trying > to figure out the best way to build the assemblies. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
