This is a nasty problem induced by the Windows wow64 emulation layer that allows 32-bit code to run on the 64-bit version of Windows. It swallows exceptions in the code that triggers the Load event. Preventing the debugger from seeing it and stepping in.
This is apparently hard to fix, the Windows and DevDiv groups at Microsoft are pointing fingers back and forth. DevDiv can't do anything about it, Windows thinks it is the correct behavior, mysteriously as that sounds. It is only a problem with a debugger attached, your code will bomb as usual without one.
In my experience, I only see this issue when I'm running with a debugger attached. The application behaves the same when run standalone: the exception is not swallowed.
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.