Are you saying it can be done in principle but isn't implemented, or that it is already implemented?
I've looked further at Application, and once you have called Shutdown, you can't call startup again, so I'm afraid your suggestion wouldn't work. Any other ideas? On 13 Feb, 21:50, "Jeff Brown" <[EMAIL PROTECTED]> wrote: > It can be done but I'm afraid you'd find it prohibitively expensive. > Setting up and tearing down an AppDomain is quite costly because the > libraries used by the new AppDomain must be freshly reloaded. Of lesser > concern here is the imposition of a remoting boundary for all > communication between AppDomains. > > I don't see why you can't ShutDown and recreate the Application at will > between tests as part of the TearDown cycle. Admittedly I haven't > worked with WPF so I've no clue whether there are other impediments to > doing so. > > Jeff. > > > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > > On Behalf Of Sam > Sent: Saturday, February 10, 2007 11:42 AM > To: MbUnit.User > Subject: MbUnit Running Tests (or TestFixtures) in fresh AppDomains > > Hi, > Is it possible to configure MbUnit so that it runs each test in a > fresh AppDomain? > > The reason I want to do this is because I am testing my application that > inherits from System.Windows.Application (the WPF application object), > and there can only be one of these per AppDomain. > > If it is not possible now, could it be added in the future? > > Thanks, > > Sam- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
