Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / December 2007

Tip: Looking for answers? Try searching our database.

Missing "cross-thread" MDA?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Peter Duniho - 11 Dec 2007 08:30 GMT
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

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.