It's funny in way. I do like .NET 2.0, but some of reports I've been hearing regardings bugs in the Visual Studio do put you off.
I have been working on a some code (part of a data transformation application), and today I finally had enough coded to start debugging it. I then started running into problems, including a slow editor, and finally this message:
ContextSwitchDeadlock was detected
Message: The CLR has been unable to transition from COM context 0x1b1ab0 to COM context 0x1b1c20 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.
Have had this message a couple of times, in slightly different situations, but once it was trying to return from one of my functions (last line of function, hit F10).
Ok, so the computer it is running on has had the betas & CTP's installed on it, but...
I'm assuming this is Visual Studio doing baaad things. The only good thing is that VS does not actually crash but allows me to continue...
Print | posted on Tuesday, January 31, 2006 6:13 PM