![]() |
|
|
Welcome to the { mindfrost82.com } forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
Missing "cross-thread" MDA?
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 |
|
|||
|
Re: Missing "cross-thread" MDA?
On Tue, 11 Dec 2007 00:30:26 -0800, Peter Duniho
<NpOeStPeAdM@nnowslpianmk.com> wrote: > 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 |
![]() |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|