For me, there is a very simple answer to this questions. The process of building a software package involves many tasks. Only one of these tasks is the actual compilation of the source into binaries. Hence, only one of these tasks can be done by Visual Studio (that's a slight over-simplification). All the other tasks, such as creating API documentation (NDoc), running unit tests (NUnit), performing code coverage (NCover) and code analysis (FxCop), interacting with you source control system (NAntContrib), packaging (NAnt), and any other custom steps must be orchestrated some other way. One choice is DOS batch or command files (yuck). Another is NAnt. Until MS Build arrives, there really aren't any other viable choices. Once MS Build hits the streets, I think there will be a renewed and valid debate between that and NAnt, but for today, there aren't any other options worth considering.
- Tom ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
