Unhandled exception catching on secondary threads.

=?Utf-8?B?TWlrZSBCaW5 rcw==?= <Mi*******@disc ussions.microso ft.com> wrote
in news:7E******** *************** ***********@mic rosoft.com:

I wish to make sure all unhandled exceptions (UE) are handled by a
central handler.

While I'm not sure this deals with your question directly, there is one
thing you need to keep in mind when using AppDomain.Unhan dledException.

AppDomain.Unhan dledException is NOT a "handler" for the exception - it is
just something that the framework uses to notify you that an exception has
occurred.

I dealt with a similar issue recently as I was developing some code for
handling plugins. The details depend on which version of .NET you are
running. If I remember correctly, the following applies:

In .NET 1.1, exceptions thrown on other threads die away without causing
the application to die.

In .NET 2.0, exceptions thrown on other threads will cause the application
to die.

See the following: (watch the URL wrap)

http://lab.msdn.microsoft.com/Produc...Feedback.aspx?
feedbackId=FDBK 21092

A quote from the above URL: "As it turns out, the documentation of
UnhandledExcept ion is incorrect. (It's always been incorrect; I've filed a
bug to get it fixed.) The UnhandledExcept ion event handler is just a
notification that an exception has gone unhandled. Registering an event
handler does not actually handle the exception; it just handles the event."

-mdb

Hi,

Take a look at Application.Thr eadException
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Mike Binks" <Mi*******@disc ussions.microso ft.com> wrote in message
news:7E******** *************** ***********@mic rosoft.com...

I wish to make sure all unhandled exceptions (UE) are handled by a central
handler.
For primary thread UEs, this may be done by

string exceptionText;

AppDomain.Curre ntDomain.Unhand ledException +=
delegate(object sender, UnhandledExcept ionEventArgs e)
{
exceptionText = e.ExceptionObje ct.ToString();
};

However, this does not work for UEs thrown from a secondary thread like
the
timer object (not the forms control).

In this case, the secondary thread is not known until the timer event
fires.

Any ideas please?
--
Mike Binks
Progressive Gaming Corp.

Mike,
I recently put a lot of this information together in one place, so this
article

http://www.eggheadcafe.com/articles/20051205.asp

may be helpful. As Michael pointed out, AppDomain.Unhan dledException
is NOT an "exception handler".
Cheers,
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Mike Binks" wrote:

I wish to make sure all unhandled exceptions (UE) are handled by a central
handler.
For primary thread UEs, this may be done by

string exceptionText;

AppDomain.Curre ntDomain.Unhand ledException +=
delegate(object sender, UnhandledExcept ionEventArgs e)
{
exceptionText = e.ExceptionObje ct.ToString();
};

However, this does not work for UEs thrown from a secondary thread like the
timer object (not the forms control).

In this case, the secondary thread is not known until the timer event fires.

Any ideas please?
--
Mike Binks
Progressive Gaming Corp.