AppDomain.UnhandledException: Removing the default handler!

[Martin Lapierre]

How can I remove the default exception handler handler?
When adding a custom handler, I can't get rid of the VS.NET unhandled
exception dialog.

Ex:
AppDomain currentDomain = AppDomain.CurrentDomain;
currentDomain.UnhandledException += new
UnhandledExceptionEventHandler(MyHandler);

MyHandler gets called AFTER the default VS.NET unhandled exception handler
(even in Release versions).

[Steven John Pack]

Are you catching Application.ThreadException as well???
"Martin Lapierre" <la*******@cedrom-sni.com> wrote in message
news:ed**************@TK2MSFTNGP09.phx.gbl...

How can I remove the default exception handler handler?
When adding a custom handler, I can't get rid of the VS.NET unhandled
exception dialog.

Ex:
AppDomain currentDomain = AppDomain.CurrentDomain;
currentDomain.UnhandledException += new
UnhandledExceptionEventHandler(MyHandler);

MyHandler gets called AFTER the default VS.NET unhandled exception handler
(even in Release versions).

[Martin Lapierre]

I don't have worker threads. I tried what you said, but that handler isn't
called.

I just want to get rid of the jit debugger. There should be a way of
removing the default handler delegate from the registered events.

"Steven John Pack" <[e-mail]> wrote in message
news:3f********@news.comindico.com.au...

Are you catching Application.ThreadException as well???
"Martin Lapierre" <la*******@cedrom-sni.com> wrote in message
news:ed**************@TK2MSFTNGP09.phx.gbl...

How can I remove the default exception handler handler?
When adding a custom handler, I can't get rid of the VS.NET unhandled
exception dialog.

Ex:
AppDomain currentDomain = AppDomain.CurrentDomain;
currentDomain.UnhandledException += new
UnhandledExceptionEventHandler(MyHandler);

MyHandler gets called AFTER the default VS.NET unhandled exception handler (even in Release versions).