Frank Racis
2003-07-04 10:16:30 UTC
The unhandled exception dialog is horrible. At an absolute minimum, it
needs to display the name of the exception. The message would be nice, as
would a "more info" button to show the stack trace and the rest of the gory
details. In its current state, it gives absolutely no useful information.
I just wasted half a day trying to troubleshoot a missing DLL. The
Framework SDK's steadfast refusal to install on XP Tablet didn't help the
situation.
Outputting to stderr doesn't do much for WinForms apps - you normally never
see it, even if you launch from a command line. Here's a hint for the next
person to run into this error. Run your application from the command line,
redirecting stderr to a file:
myapp.exe 2> error.log
When the application dies, the exception information and stack dump will be
written to the file. (I wish I had figured this out 4 hours ago).
-Frank
needs to display the name of the exception. The message would be nice, as
would a "more info" button to show the stack trace and the rest of the gory
details. In its current state, it gives absolutely no useful information.
I just wasted half a day trying to troubleshoot a missing DLL. The
Framework SDK's steadfast refusal to install on XP Tablet didn't help the
situation.
Outputting to stderr doesn't do much for WinForms apps - you normally never
see it, even if you launch from a command line. Here's a hint for the next
person to run into this error. Run your application from the command line,
redirecting stderr to a file:
myapp.exe 2> error.log
When the application dies, the exception information and stack dump will be
written to the file. (I wish I had figured this out 4 hours ago).
-Frank
Mike is correct. The message you are getting simply means that there is
anunhandled exception in your code somewhere. Attaching a debugger to the
binary is an easy way to investigate this issue. Also, when you click Ok
the exception information and guilty stack trace should be output to
stdoutbinary is an easy way to investigate this issue. Also, when you click Ok
the exception information and guilty stack trace should be output to
and stderr for your process.
Mark Gabarra
MS CLR team
Mark Gabarra
MS CLR team