nunit-core team mailing list archive

[KYL <zionyx@xxxxxxxxx>]

Hi David,

I dont think the 3rd party DLL use WCF. It's a tool that communicates
with a device driver, wrapped by a VC++ project.

Line 69 in my test codes generally trying to loop through a null referenced list like this:
            foreach (IDataSequenceGroupOutput group in baseGroup.OutputGroups)

But the unhandled exception ONLY occurred when i test my dll with a
wrong version of the 3rd party DLL file. After i updated the 3rd party
DLL file with the right version, the unhandled exception disappeared,
still nunit-console.exe got stuck indefinitely until Ctrl+C is pressed.

I know this is caused by accessing a NULL referenced variable, but i hope nunit-console.exe does not get stuck due to this.
NUnit performs the tests without problems, the test failed but it wasn't stuck.

Do you still need more info?

Regards,
KYL

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