Chris,
Mono uses access violations to implement null reference exceptions on
Windows (IIRC). Mono handles these normally during program flow. However,
when the debugger is attached it handles them before mono can. I don't know
of a way to avoid this behavior. Normally, I just issue an assert
I'm working on an interesting project when I'm using a project called
Firebreath to create an NPAPI browser plugin which loads an embedded mono
runtime to do things we want to do. To test this app, I'm attaching Visual
Studio to all the Chrome processes and stepping through things. What's
happening
