Okay, I'm guessing I'm overlooking something simple here, but I'm
obviously not going to find it.
Someone please tell me the exact name of the "Cross-thread operation not
valid" MDA, as seen in the "Managed Debugging Assistants" list in the
Debug/Exceptions... menu of Visual Studio 2005?
I'm looking for this exception in my own VS configuration, to verify that
it's turned on because I accidently wrote some code that _should_ have
caused the exception but didn't. I can't even find the exception in the
list of MDAs.
Is it possible for an MDA to just get removed somehow? If so, how do I
get it back?
This is so weird...
Thanks,
Pete
Peter Duniho - 11 Dec 2007 08:46 GMT
> Okay, I'm guessing I'm overlooking something simple here, but I'm
> obviously not going to find it.
Yay...it worked! The classic "post the question and minutes later you
will figure it out yourself" solved the crime. :)
I had mis-remembered the cross-thread exception as being an MDA
exception. It's not...it's just a normal InvalidOperationException,
thrown by the Control class for invalid cross-thread calls. Controllable
via the CheckForIllegalCrossThreadCalls property.
As for why it wasn't firing when I thought it should be, apparently I was
wrong about when it should be (as is, apparently, the MSDN
documentation). Or maybe the class simply failed to check for the illegal
operation in the specific call I made (Control.Invalidate()). I'm not
really sure yet about that.
Anyway, sorry to take your time. :)
Pete