nunit-core team mailing list archive

[David Schmitt <david@xxxxxxx>]

P.P.S: I've tested this with 2.5.3. The error occurs on any "/domain"
setting when "/process=Single", but does NOT happen when using
"/domain=None|Single /process=Separate".

"/domain=Multiple /process=Separate" and "/process=Multiple" hang in
setup while waiting for the worker thread to start.

-- 
Bug 686560 AppDomainUnloadedException not fixed
https://bugs.launchpad.net/bugs/423611
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.

Status in NUnit Test Framework: Invalid
Status in NUnit V2 Test Framework: Incomplete

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?