Sign in
in
   
"It is the mark of an educated mind to be able to entertain a thought without accepting it."  -Aristotle

About Me

I am a co-founder of Notches, an early stage startup currently based in NYC. We are building a free, open reviews network that anyone can participate in and anyone can build on top of. You can find out more on our official blog.

Read more about my background.

Connect with me on...

Recent Readers

Flickr Photos

 

Warning:

This article is more than 45 days old. Given the speed at which the technology world moves, this post is probably somewhat out of date. Please keep this in mind when reading the post. If this is a tutorial, please check whether you are using the same versions mentioned in the article.

Speaking of Exceptions...

Speaking of exceptions, here are two great error messages passed along by Dave.

This one might be the most verbose I've ever seen:

ContextSwitchDeadlock was detected

Message: The CLR has been unable to transition from COM context 0x15a948 to COM context 0x15a7d8 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.

[ For those of you looking for a solution to this, check the link that Josh posts below  ]

This one, from Outlook, is just funny:

Window is disabled: cannot close. Check your code.

Only published comments... Jan 04 2006, 08:07 AM by Tim

View related posts

 

Josh Einstein said:

Ha! I just encountered this exception today while stepping through code in the debugger. I guess it's so long and verbose so that it gets noticed. It's actually a very serious problem. One that Microsoft is having a very hard time solving in the architecture of the next presentation platform.

If you've got alot of time on your hands, here's a blog posting about it.
http://blogs.msdn.com/cbrumme/archive/2004/02/02/66219.aspx
January 31, 2006 6:49 PM