Gary, >>>why not just right a shell script (bash, not Windows shell) wrapper for calling >>>NAnt?
For one reason, we are all running on Windows, so bash isn't automatically available. Yes, I know we could install a Windows version of bash, but I don't want to get into the position of having to tell everyone who uses my NAnt script to install a Unix utility just to fire up a script which could be run by itself anyway. The second reason is that I don't think it's desirable to use two totally different languages to do one job if one language could do it all. Yes, there are special cases, but I don't think my current usage qualifies. Using one script for three situations may sound like too much into one program, but I don't think it is. The nightly build would use the -D:msi command line parameter. If that parameter is present, then I do a silent uninstall followed by a silent install of the specified MSI package. At that point, I have the product in "the standard location." The developers would use the -D:buildroot parameter, when you might call a non-standard location, but it's still the same directory structure. Therefore, 90+% of the script is written totally in terms of a NAnt property pointing to the installation to use. Merrill ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
