Stopping application crashing when there is an unhandled exception

[joseph_gallagher]

Hi,

I've recently ported a .Net 1.1 application to .Net 2.0 and the one new
feature that is getting on my nerves is that when there is an unhandled
exception the application completely crashes, causing user to loose all
the work they have done where they could previously just click continue
and in 99% of cases be fine. Is there an option to turn this annoying
crash and loose everything option off, I can see it has its merits but
in my case its just annoying.

Joe.

[Mark Rae]

<jo************ **@hotmail.comw rote in message
news:11******** *************@s 34g2000cwa.goog legroups.com...

I've recently ported a .Net 1.1 application to .Net 2.0 and the one new
feature that is getting on my nerves is that when there is an unhandled
exception the application completely crashes, causing user to loose all
the work they have done where they could previously just click continue
and in 99% of cases be fine. Is there an option to turn this annoying
crash and loose everything option off, I can see it has its merits but
in my case its just annoying.

Well, the first question I guess is why might there be an unhandled
exception...? Are you not using exception handling i.e.
Try...Catch[...Finally]?

Secondly, why does your Global.asax not have an Application_Err or
routine...?

[joseph_gallagher]

Mark Rae wrote:

<jo************ **@hotmail.comw rote in message
news:11******** *************@s 34g2000cwa.goog legroups.com...

I've recently ported a .Net 1.1 application to .Net 2.0 and the one new
feature that is getting on my nerves is that when there is an unhandled
exception the application completely crashes, causing user to loose all
the work they have done where they could previously just click continue
and in 99% of cases be fine. Is there an option to turn this annoying
crash and loose everything option off, I can see it has its merits but
in my case its just annoying.

Well, the first question I guess is why might there be an unhandled
exception...? Are you not using exception handling i.e.
Try...Catch[...Finally]?

Secondly, why does your Global.asax not have an Application_Err or
routine...?

The main cause of exceptions has been cross thread exceptions on
controls, which I know can be set to be allowed but I do want to root
them all out. Also as a general preference if a new bug finds its way
in I'd prefer the user to at least have the option to try to continue.

It handles the "AppDomain.Curr entDomain.Unhan dledException" to log the
problem if thats what you mean, but after this the application still
exits.

All I'm really asking is there a way to avoid the application closing
on an unhandled exception, not how to avoid unhandled exceptions.

[Mark Rae]

<jo************ **@hotmail.comw rote in message
news:11******** *************@1 1g2000cwr.googl egroups.com...

It handles the "AppDomain.Curr entDomain.Unhan dledException" to log the
problem if thats what you mean, but after this the application still
exits.

All I'm really asking is there a way to avoid the application closing
on an unhandled exception, not how to avoid unhandled exceptions.

http://www.developer.com/net/asp/article.php/961301

[Willy Denoyette [MVP]]

<jo************ **@hotmail.comw rote in message
news:11******** *************@1 1g2000cwr.googl egroups.com...

>
Mark Rae wrote:

><jo*********** ***@hotmail.com wrote in message
news:11******* **************@ s34g2000cwa.goo glegroups.com.. .

I've recently ported a .Net 1.1 application to .Net 2.0 and the one new
feature that is getting on my nerves is that when there is an unhandled
exception the application completely crashes, causing user to loose all
the work they have done where they could previously just click continue
and in 99% of cases be fine. Is there an option to turn this annoying
crash and loose everything option off, I can see it has its merits but
in my case its just annoying.

Well, the first question I guess is why might there be an unhandled
exception... ? Are you not using exception handling i.e.
Try...Catch[...Finally]?

Secondly, why does your Global.asax not have an Application_Err or
routine...?

The main cause of exceptions has been cross thread exceptions on
controls, which I know can be set to be allowed but I do want to root
them all out. Also as a general preference if a new bug finds its way
in I'd prefer the user to at least have the option to try to continue.

It handles the "AppDomain.Curr entDomain.Unhan dledException" to log the
problem if thats what you mean, but after this the application still
exits.

All I'm really asking is there a way to avoid the application closing
on an unhandled exception, not how to avoid unhandled exceptions.

What do you mean with " cross thread exceptions on controls"? Web controls don't have thread
affinity, why should you ever get this kind of exceptions? Am I missing something?

Willy.

[Marc Gravell]

What do you mean with " cross thread exceptions on controls"? Web

controls don't have thread affinity, why should you ever get this
kind of exceptions? Am I missing something?

Unless I blinked, the OP never mentioned web; Mark did (via
Global.asax)

Marc

[joseph_gallagher]

Mark Rae wrote:

<jo************ **@hotmail.comw rote in message
news:11******** *************@1 1g2000cwr.googl egroups.com...

It handles the "AppDomain.Curr entDomain.Unhan dledException" to log the
problem if thats what you mean, but after this the application still
exits.

All I'm really asking is there a way to avoid the application closing
on an unhandled exception, not how to avoid unhandled exceptions.

http://www.developer.com/net/asp/article.php/961301

Its a application, not web application

[Mark Rae]

"Marc Gravell" <ma**********@g mail.comwrote in message
news:ud******** ******@TK2MSFTN GP04.phx.gbl...

>What do you mean with " cross thread exceptions on controls"? Web
controls don't have thread affinity, why should you ever get this kind of
exceptions? Am I missing something?

Unless I blinked, the OP never mentioned web; Mark did (via Global.asax)

Apologies for causing any confusion - I quoted the link as an example of
global exception handing - probably should have looked for a WinForms one,
really...

[Boban Stojanovski]

You should handle unhandled exceptions :).

Code in your Program class will be like this:
//Main method:

Application.Thr eadException += new
ThreadException EventHandler(On ThreadException );
AppDomain.Curre ntDomain.Unhand ledException +=
new UnhandledExcept ionEventHandler (CurrentDomain_ UnhandledExcept ion);

Application.Ena bleVisualStyles ();
Application.Set CompatibleTextR enderingDefault (false);
Application.Run (new formMDI());

//event handlers
private static void CurrentDomain_U nhandledExcepti on(object sender,
UnhandledExcept ionEventArgs e)
{
MessageBox.Show ("CurrentDomain _UnhandledExcep tion: " +
e.ExceptionObje ct);
}

private static void OnThreadExcepti on(object sender,
ThreadException EventArgs t)
{
MessageBox.Show ("OnThreadExcep tion: " + t.Exception);
}

Best Regards,
Boban

*** Sent via Developersdex http://www.developersdex.com ***

[joseph_gallagher]

Boban Stojanovski wrote:

You should handle unhandled exceptions :).

Code in your Program class will be like this:
//Main method:

Application.Thr eadException += new
ThreadException EventHandler(On ThreadException );
AppDomain.Curre ntDomain.Unhand ledException +=
new UnhandledExcept ionEventHandler (CurrentDomain_ UnhandledExcept ion);

Application.Ena bleVisualStyles ();
Application.Set CompatibleTextR enderingDefault (false);
Application.Run (new formMDI());

//event handlers
private static void CurrentDomain_U nhandledExcepti on(object sender,
UnhandledExcept ionEventArgs e)
{
MessageBox.Show ("CurrentDomain _UnhandledExcep tion: " +
e.ExceptionObje ct);
}

private static void OnThreadExcepti on(object sender,
ThreadException EventArgs t)
{
MessageBox.Show ("OnThreadExcep tion: " + t.Exception);
}

Best Regards,
Boban

*** Sent via Developersdex http://www.developersdex.com ***

I have similar code in my app, but after the UnhandledExcept ion is
handled, the application still exits, what I need is to be able to
continue running the program like you can in .Net 1.1