Tomas Restrepo wrote > The basic idea would be to completely brake off the dependency in the NUnit > classes to the NAnt Element-derived classes, possibly through the use of a
>couple of data objects. The problem right now is that instances of NUnitTest >(which is Element-derived) is passed all around the code, all the way >through the ResultFormatters, just to carry some data. Instead, I'd like to >contain all that data into a separate class, and make that one serializable, >which would avoid us having to touch all the other NAnt classes. > > This sounds much better. Refactoring that number of classes to get one task working properly would be a bit out of proportion. >Once that is done, we should be able to completely instantiate an >NUnitTestRunner _inside_ the other appdomain, without giving it any more >info (right now, you need to manipulate lots of properties in a >cross-appdomain way, such as the formatters collection). > >The only downside I can see to this is that there's a chance you wouldn't be >able to use the default LogFormatter in this scenario, but I haven't checked >that throughly... > >If no one has any problems with this, I'l start working on this tomorrow. > >-- > Awesome. Go for it. btw do you think we should still call it fork ? The Ant version actually launches a new VM to run the tests. However fork is shorter than runInNewAppdomain. Any better ideas ? Ian ------------------------------------------------------- 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
