The original bug (NUnit throwing an exception when trying to unload the test
appdomain) has been fixed.
There was some code that required access to the domain being executed outside a
try block.
David's sample code seems to be a timing problem that could occur under various
circumstances - any situation
that gave allowed the unload to execute before the host had finally stopped. No
changes made to NUnit for this.
Any future bugs around domain unloading should avoid conflating NUnit's own use
of domains with those
domains created by the test or SUT.
Charlie
** Changed in: nunitv2
Status: Confirmed => Fix Committed
--
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: Fix Committed
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 : nunit-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nunit-core
More help : https://help.launchpad.net/ListHelp
