nunit-core team mailing list archive

[David Schmitt <david@xxxxxxx>]

Hi,

the attached zip archive contains a solution which demonstrates the bug.
Running the resulting AppDomainUnloadedExceptionBugDemo.exe from the
command line produces the same (trace-)output as running from nunit, but
doesn't throw the exception.

Please consider this now as a real bug!


Thanks for your time and work,

David Schmitt

P.S: you need to "netsh http add urlacl url=http://+:6666/Service
user=%myusername%" as administrator to allow the example to run at all.

** Attachment added: "example project to demonstrate the bug"
   http://launchpadlibrarian.net/38043148/AppDomainUnloadedExceptionBugDemo.zip

-- 
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?