nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

I see you have re-instated the bug, which I had previously converted to
a question.

So far, there is not enough info to treat this as a bug. It's not a general problem, nor does it appear to have anything to do with
the old bug fixed in version 2.1. That bug had to do with NUnit's unloading of its own AppDomains.

Something in your code having to do with AppDomains is apparently
causing this. To reproduce it, we need to know what that code is
actually doing. Can you provide a short test that demonstrates the
problem?

[As an aside, I'm guessing somebody recommended the "work-around
disabling legacyUnhandledExceptionPolicy" to you. This is not anything I
would recommend. NUnit requires this setting in it's own config file and
it should not be removed.]

Charlie

** Changed in: nunitv2
       Status: New => Incomplete

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