How to force the program to continue after unhandled exception detection

Hi

For my winforms app (.net 2.0) I have defined a general exception
handler:

Application.ThreadException +=
new
System.Threading.ThreadExceptionEventHandler(Application_ThreadException);

//....

void Application_ThreadException(object sender,
System.Threading.ThreadExceptionEventArgs e) {
//show a decent message
}

Ok, the thing is that when in debugging mode and an unhandled
exception occurs, the exception helper pops up.
On this point, I'm stucked. Can't get rid of exception helper, even if
I want the exception to be handled by the general exception handler I
defined.
I have played with exception settings (CTRL-D, E), but no luck.
I really need to keep this design, so I need to be able to let the
program to continue execution.
How to do this?

Thanks.
.

Relevant Pages

  • Re: Try Finally...
    ... Now we can protect every more or less specialized action ... an error indication (exception or error code) has to be ... an according exception handler can be inserted into the code. ... resources, as they are related to specific actions. ...
    (comp.lang.pascal.delphi.misc)
  • Re: WinForms bug? ThreadException not invoked on Exceptions in system code pre-processing the me
    ... Message Queue and invoking the appropriate handler. ... if an Exception is raised during the PRE-PROCESSING of a Windows ... And because any handling will probably fail if there is no memory, the CLR will terminate the application without attempting to call the ApplicationException or UnhandledException events. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: BackgroungWork taske ended for no appearent reason
    ... To do the same thing with Try/Catch blocks requires wrapping every file access with a Do While ... ... If there was any exception thrown in your DoWork event handler, ... If the operation raises an exception that your code does not handle, ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Frame-based exception handling problem on Server 2008
    ... In this case, the exception ends fatal, usually Cygwin creates a stack ... The Cygwin DLL is a POSIX ... handler is supposed to be *the* exception handler for Cygwin ... It also does not know if the signal handler returns or not. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Frame-based exception handling problem on Server 2008
    ... If I set a breakpoint to our exception ... points to the default handler, our exception handler is called just fine. ... typedef struct _exception_list ...
    (microsoft.public.win32.programmer.kernel)