While looking at an exception that is being thrown in Visual Studio 2005's popup window for exceptions I got the following error:

ContextSwitchDeadlock was detected
Message: The CLR has been unable to transition from COM context 0x1a09c0 to COM context 0x1a0b30 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.

The link for more help took me into the topic on Diagnosing Errors with Managed Debug Assistants. The link is ms-help://MS.VSCC.v80/MS.MSDN.v80/MS.VisualStudio.v80.en/dv_fxdebug/html/76994ee6-9fa9-4059-b813-26578d24427c.htm in my help file. I didn't even know that these things exist. That is one of the cool things about the .NET Framework, there are so many things provided for you that are so useful that each day is an adventure.