Tomas, If the fork attributes would be removed and set to true internally, and (only) the NAntContrib tests would be run using the command line runner, would there be other problems that need to be solved to make the NUnit2 task work for real-world usage?
Bernard > -----Original Message----- > From: Tomas Restrepo [mailto:[EMAIL PROTECTED]] > Sent: Friday, November 22, 2002 4:25 AM > To: [EMAIL PROTECTED] > Subject: Re: NUnit 2 support (was: RE: [nant-dev] FAQ: The > next NAnt version) > > > John, > > > I noticed that NUnit2Task was executing very different code > based on the > > fork attribute; code that looks suspiciously like the > current code in > > nunit-console. > > I'd like to refactor that code slightly, but that's a different thing > altogether :) > > > Maybe this is a simpler workaround than using exec? > > It is a good workaround for many apps. However, I'd like to > point out two > things: > > - With the current NUnit2 architecture, the fork="false" (the default) > option makes no sense, as it really, really, only serves to test nant > itself. In fact, fork="true" should be the default, as that > was how NUnit2 > was concieved: a new appdomain is created, and assemblies to > test are loaded > into that appdomain from inside itself (hence all the > problems we have). > > -Even with fork="true", nantcontrib tests still cannot run. > The problem is > that nantcontrib requires both access to nantcontrib's and > nants dlls, and > with the current architecture this is hard to do without some > rather ugly > hacks (at least as I see it). > > -- > Tomas Restrepo > [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
