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.

Go Back   { mindfrost82.com } > Gadget Corner > Tech Newsgroups > Microsoft > .NET Framework

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-11-2007, 08:30 AM
Peter Duniho
 
Posts: n/a
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
Reply With Quote
  #2 (permalink)  
Old 12-11-2007, 08:46 AM
Peter Duniho
 
Posts: n/a
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
Reply With Quote
Reply

  { mindfrost82.com } > Gadget Corner > Tech Newsgroups > Microsoft > .NET Framework


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 11:11 AM.


Powered by vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.1.0 ©2007, Crawlability, Inc.
© 1999-2008 mindfrost82.com v11.0


Sponsors:
Books | Buy Anything On eBay | Credit Card | Web Advertising | Credit Counseling



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114