HELP: Debugging ApplicationEvents.UnhandledException???

[Guest]

Hi all,

When I'm debugging my application in VS.NET 2005, the debugger intercepts
all unhandled exceptions and does not break into
ApplicationEvents.UnhandledException.

How do I debug ApplicationEvents.UnhandledException? I have some elaborate
code in there which I would like to test.

ApplicationEvents.UnhandledException only seems to be executed if I do not
have a debugger attached.

Thanks!

 

[Guest]

Hi all,

When I'm debugging my application in VS.NET 2005, the debugger
intercepts all unhandled exceptions and does not break into
ApplicationEvents.UnhandledException.

How do I debug ApplicationEvents.UnhandledException? I have some
elaborate code in there which I would like to test.

ApplicationEvents.UnhandledException only seems to be executed if I do
not have a debugger attached.

Thanks!

Just bumping up the post ... anyone know how?

Thanks!

 

[RobinS]

You could run it w/o debugging. (Debug/Start without debugging).

Robin S.
---------------------------------

 

[Guest]

You could run it w/o debugging. (Debug/Start without debugging).

Yes I know that - But I want to debug

 

[Randy]

I'm just a beginner so take this with a grain of salt:
I think you want to test your exception handlers? What about using Err.Raise
Example:
Try
Err.Raise(61) 'raise disk full error
Catch when Err.Number = 61
MsgBox("Error: Disk is full")
End Try

Randy

 

[Guest]

I'm just a beginner so take this with a grain of salt:
I think you want to test your exception handlers? What about using
Err.Raise Example:
Try
Err.Raise(61) 'raise disk full error
Catch when Err.Number = 61
MsgBox("Error: Disk is full")
End Try

Hi Randy, I'm already testing my exceptions through out my application.

I would like to debug my global exception handler (for cases where my error
handling falls through).

Unfortunately it seems while in debug mode, VS.NET takes over the global
handler... and doesn't allow me to debug my custom code :-(