Why is Visual Studio breaking on an unhanded exception running unit tests?

There's nothing quite as nasty as an AccessViolation exception, only StackOverflow is worse. I can make out "communication", that unmanaged code probably runs in a thread that neither the CLR nor the test runner knows anything about. Very limited options there, no way to make a thread like that simply seize to exist.

This is probably from your application trying to read memory that belongs to another process/thread/class. These things are protected by the operating system, so can't be ignored by an application.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.