news:1143569984.794811.225140@i40g2000cwc.googlegroups.com...
> Good question that I'd like an answer to also.  I got your error
> message also today.  I got a run time error on my target computer and
> decided to process the data on my development computer and step through
> it in the debugger to see exactly what was going wrong.  Well I was
> stepping through a perfectly benign for loop and at random times it
> would either give the message you listed (about pumping, apartments,
> and threads), or just hang.  When it hung, it was supposed to step on a
> perfectly fine code statement, like an endif statement or a boolean
> test in an if statement. (The line of code that it would hang on would
> vary from run to run.)   Then it would make a sound like it was hitting
> a breakpoint, even though the next statement didn't have a break point
> set there.  There was no yellow arrow, no highlighted line of code,
> nothing.  If I clicked on the Go triangle again, it would say, from a
> balloon in the task tray,
>
> "Microsoft Visual Studio Delay Notification
> Microsoft Visual Studio is waiting for an internal operation to
> complete. If you regularly encounter this delay during normal usage,
> please report this problem to Microsoft."
>
> The only way to get out of it was to kill off my app's executable that
> was running (via Task manager or right-clicking in the task bar and
> saying "Close Group".  Then it would return to the development
> environment.
> I went to lunch and came back and then everything was OK - I couldn't
> get anything strange to happen again.  This after hours of pumping and
> waiting messages before lunch!  I still don't know what happened.  Let
> me know if anyone else has encountered these strange messages.
>

> Good question that I'd like an answer to also.  I got your error
> message also today.  I got a run time error on my target computer and
> decided to process the data on my development computer and step through
> it in the debugger to see exactly what was going wrong.  Well I was
> stepping through a perfectly benign for loop and at random times it
> would either give the message you listed (about pumping, apartments,
> and threads), or just hang.  When it hung, it was supposed to step on a
> perfectly fine code statement, like an endif statement or a boolean
> test in an if statement. (The line of code that it would hang on would
> vary from run to run.)   Then it would make a sound like it was hitting
> a breakpoint, even though the next statement didn't have a break point
> set there.  There was no yellow arrow, no highlighted line of code,
> nothing.  If I clicked on the Go triangle again, it would say, from a
> balloon in the task tray,
>
> "Microsoft Visual Studio Delay Notification
> Microsoft Visual Studio is waiting for an internal operation to
> complete. If you regularly encounter this delay during normal usage,
> please report this problem to Microsoft."
>
> The only way to get out of it was to kill off my app's executable that
> was running (via Task manager or right-clicking in the task bar and
> saying "Close Group".  Then it would return to the development
> environment.
> I went to lunch and came back and then everything was OK - I couldn't
> get anything strange to happen again.  This after hours of pumping and
> waiting messages before lunch!  I still don't know what happened.  Let
> me know if anyone else has encountered these strange messages.