Note to All: Their are (at least) two bugs being conflated here, which makes it a bit more difficult to resolve. If you add any problems on, please indicate _which_ of the two situations apply:
1. The original bug, also referenced in comment 12, with a stack trace that indicates an exception thrown when NUnit itself is unloading an AppDomain. 2. An exception thrown when your own code (test or under test) attempts to unload an AppDomain. #2 could be a bug in NUnit or in your own code, depending on the details. Under no circumstances should you unload the actual test assembly while NUnit is using it. Charlie -- Bug 686560 AppDomainUnloadedException not fixed https://bugs.launchpad.net/bugs/423611 You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. Status in NUnit Test Framework: Invalid Status in NUnit V2 Test Framework: Confirmed Bug description: Though it was stated in NUnit 2.1 release notes that the bug "686560 - AppDomainUnloadedException in nunit-console" is fixed/closed, I still get this in NUnit 2.4.7. This time I get it when I try AppDomain.Unload() which is definitely not unloaded. No exceptions thrown by Visual Studio. We can not rely on the work-around disabling "legacyUnhandledExceptionPolicy" in configs. Any fixes for this? _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : [email protected] Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
