E
Ed White
I'm using VB (VS 2008) to create a VSTO project with Excel 2007. When I run
my VSTO project, it loads Excel and starts running my code. Sometimes while
the VSTO is running, I shift the focus to another program (e.g. look at an IE
web page or read an Outlook email), and while the focus is shifted to the
other program, the VSTO generates an exception. When the exception occurs, I
hear an error beep, the taskbar at the bottom for Excel starts flashing red,
and apparently there is an error/dialog window (somewhere) asking for user
input. The problem is, no matter what I do, I can't see the error window
(I've tried everything, including using the Task Manager to switch focus,
cascading the windows, minimizing all the open windows, etc.) Only if I stop
the program (in which case another window does pop us saying a dialog window
is open--are you sure you want to stop?), run mu VSTO code again without
touching anything else on the PC while the VSTO is running, can I then see
the error window when it pops up (it turns out it was a ContextSwitchDeadlock
error--incidentally, I just went into VS options and unchecked the Thrown box
for that error). Do you have any suggestions how can I get the hidden dialog
window to become visible?
my VSTO project, it loads Excel and starts running my code. Sometimes while
the VSTO is running, I shift the focus to another program (e.g. look at an IE
web page or read an Outlook email), and while the focus is shifted to the
other program, the VSTO generates an exception. When the exception occurs, I
hear an error beep, the taskbar at the bottom for Excel starts flashing red,
and apparently there is an error/dialog window (somewhere) asking for user
input. The problem is, no matter what I do, I can't see the error window
(I've tried everything, including using the Task Manager to switch focus,
cascading the windows, minimizing all the open windows, etc.) Only if I stop
the program (in which case another window does pop us saying a dialog window
is open--are you sure you want to stop?), run mu VSTO code again without
touching anything else on the PC while the VSTO is running, can I then see
the error window when it pops up (it turns out it was a ContextSwitchDeadlock
error--incidentally, I just went into VS options and unchecked the Thrown box
for that error). Do you have any suggestions how can I get the hidden dialog
window to become visible?