Hi all, > Unfortunately for us, not, it's not inherited. Basically, for a type to be > actually serializable, the type itself, and all of its base classes need to > be serializable.
OK, I've been looking at this some more, and I've come to the conclusion that perhaps all this won't be necessary. However, some hefty refactoring of the NUnit code in NAnt will need to be done. 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. 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. -- 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
