I've started looking at the NUnit task implementation, with the goal of adapting it to work with csUnit. I was surprised to see that NAnt essentially uses NUnit's AppDomain approach, to run the tests directly. While I understand why this is necessary and useful for NUnit, I don't understand why the NAnt NUnit task does it the same way, as opposed to merely using the exec approach. My expectation (coming from the UNIX world) is that it's simpler and more reliable to just execute the other program (NUnit in this case) via a command line invocation, using the existing functions that implement exec, and then parse the XML results file. Granted, this has the overhead of the additional process creation, but given how expensive tests are to begin with, the process creation overhead seems minimal in comparison.
I could get away with just using exec for the csUnit invocation, and then writing a separate task and/or program to process the results file, but that seems clunkier, plus it's impossible to get the return status from exec, as far as I know. Many thanks, Gary ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
