D
David Veeneman
I'm working on a program with two assemblies that I have written in VS.Net--
a DLL and a Windows Form app that drives it. When the CLR hits an unhandled
error in the DLL, it does not show me the error in the source code, as it
normally does. Instead, I get a dialog box that says an unhandled error has
been encountered, with a dump of the exception. The dump starts with "See
the end of this message for details on invoking just-in-time (JIT) debugging
instead of this dialog box."
To isolate the problem, I put statements in both the driver app and the DLL
to throw a test exception. The driver app exceptions takes me to the source
code for VS.Net debugging. But in the DLL, I get the dialog.
Can anyone tell my why this is happening? Are there any good articles on the
issue? Thanks in advance.
David Veeneman
Foresight Systems
a DLL and a Windows Form app that drives it. When the CLR hits an unhandled
error in the DLL, it does not show me the error in the source code, as it
normally does. Instead, I get a dialog box that says an unhandled error has
been encountered, with a dump of the exception. The dump starts with "See
the end of this message for details on invoking just-in-time (JIT) debugging
instead of this dialog box."
To isolate the problem, I put statements in both the driver app and the DLL
to throw a test exception. The driver app exceptions takes me to the source
code for VS.Net debugging. But in the DLL, I get the dialog.
Can anyone tell my why this is happening? Are there any good articles on the
issue? Thanks in advance.
David Veeneman
Foresight Systems