To revise the title, this post replaces the first one.
Since we upgraded our solutions from VS 2003 to 2005, one user is repeatedly
reporting InvalidOperationExceptions, announced to her in the form of a
window that says "XXX.exe has encountered a problem and needs to close. We
are sorry for the inconvenience .... Please tell Microsoft about this
problem." --which I'm now doing.
The latest involved the following information:
EventType: clr20r3
P1: vmed.exe
P2: 1.0.2284.37257
P3: 4431cee3
P4: system.windows.forms
P5: 2.0.0.0
P6: 4333aefa
P7: 1508
P8: 17
P9: system.invalidoperationexception
We cannot reproduce this problem. If I ask the user to repeat the operation
the error does not recur on demand. Instead the problem seems random, now
popping up here and later popping up there.
Once the error definitely was not caused by reflection or invocation. Twice
it might have been. This problem is new to VS 2005. We use C#.
We have implemented a global exception handler, based on
application.threadexception event for handling uncaught exceptions, but that
handler is not getting called for these invalid operation exceptions.
Instead this apologetic Microsoft window pops up, whereupon the user is
summarily cast out.
What can we do to solve this problem or at least identify its cause?
Randy Neall
|
Similar Threads
