Application.ThreadException

[Rakesh]

Hi,

I am catching unhandled exception by attached an event
handler on the Application.ThreadException event. This
will ensure that I could handle all uncaught exceptions
on the main thread.

But, suppose I create a new thread within my app and an
unhandled exception is generated in that thread, will
that exception be caught here?

Thanks in advance,
Rakesh

[Jan Tielens]

No, the unhandled exceptions on other threads wont be caught.

--
Greetz,
Jan
__________________________________
Read my weblog: http://weblogs.asp.net/jan
"Rakesh" <an*******@discussions.microsoft.com> schreef in bericht
news:04****************************@phx.gbl...

Hi,

I am catching unhandled exception by attached an event
handler on the Application.ThreadException event. This
will ensure that I could handle all uncaught exceptions
on the main thread.

But, suppose I create a new thread within my app and an
unhandled exception is generated in that thread, will
that exception be caught here?

Thanks in advance,
Rakesh

[Rakesh]

Hi Jan,

Thanks!

So do u mean that we have to go about the same old way of
try-catch in this case? Any other way?

Rakesh

-----Original Message-----
No, the unhandled exceptions on other threads wont be caught.
--
Greetz,
Jan
__________________________________
Read my weblog: http://weblogs.asp.net/jan
"Rakesh" <an*******@discussions.microsoft.com> schreef in berichtnews:04****************************@phx.gbl...

Hi,

I am catching unhandled exception by attached an event
handler on the Application.ThreadException event. This
will ensure that I could handle all uncaught exceptions
on the main thread.

But, suppose I create a new thread within my app and an
unhandled exception is generated in that thread, will
that exception be caught here?

Thanks in advance,
Rakesh

.

catch (Exception e)
{
}

In the main would catch everything right?
"Rakesh" <an*******@discussions.microsoft.com> wrote in message
news:05****************************@phx.gbl...

Hi Jan,

Thanks!

So do u mean that we have to go about the same old way of
try-catch in this case? Any other way?

Rakesh

-----Original Message-----
No, the unhandled exceptions on other threads wont be

caught.

--
Greetz,
Jan
__________________________________
Read my weblog: http://weblogs.asp.net/jan
"Rakesh" <an*******@discussions.microsoft.com> schreef

in bericht

news:04****************************@phx.gbl...

Hi,

I am catching unhandled exception by attached an event
handler on the Application.ThreadException event. This
will ensure that I could handle all uncaught exceptions
on the main thread.

But, suppose I create a new thread within my app and an
unhandled exception is generated in that thread, will
that exception be caught here?

Thanks in advance,
Rakesh

.

[Dave]

You can attach a handler to the AppDomain.CurrentDomain.UnhandledException
event, but be aware that one of its limitations is that it will only work
for the default appdomain.

If you create the thread yourself then you should put a try-catch block
within the thread's start function to ensure that you will catch and handle
all exceptions. For the main thread and threads that originate in unmanaged
code, an unhandled exception will terminate the app. For threads you create
manually, threadpool threads, and finalizer threads, even though your
unhandled exception handler is called, the runtime will catch and swallow
all exceptions; the IsTerminating field in the UnhandledExceptionEventArgs
is set to false.

"Rakesh" <an*******@discussions.microsoft.com> wrote in message
news:05****************************@phx.gbl...

Hi Jan,

Thanks!

So do u mean that we have to go about the same old way of
try-catch in this case? Any other way?

Rakesh

-----Original Message-----
No, the unhandled exceptions on other threads wont be

caught.

--
Greetz,
Jan
__________________________________
Read my weblog: http://weblogs.asp.net/jan
"Rakesh" <an*******@discussions.microsoft.com> schreef

in bericht

news:04****************************@phx.gbl...

Hi,

I am catching unhandled exception by attached an event
handler on the Application.ThreadException event. This
will ensure that I could handle all uncaught exceptions
on the main thread.

But, suppose I create a new thread within my app and an
unhandled exception is generated in that thread, will
that exception be caught here?

Thanks in advance,
Rakesh

.

[Rakesh]

Hi Dave,

I want to know if i got you right:

So if i have only one appdomain and i attach an event
handler in the
AppDomain.CurrentDomain.UnhandledException, will that
ensure that I can handle all the uncaught exceptions
regardless of whichever thread they are in?

Rakesh

-----Original Message-----
You can attach a handler to the AppDomain.CurrentDomain.UnhandledExceptionevent, but be aware that one of its limitations is that it will only workfor the default appdomain.

If you create the thread yourself then you should put a try-catch blockwithin the thread's start function to ensure that you will catch and handleall exceptions. For the main thread and threads that originate in unmanagedcode, an unhandled exception will terminate the app. For threads you createmanually, threadpool threads, and finalizer threads, even though yourunhandled exception handler is called, the runtime will catch and swallowall exceptions; the IsTerminating field in the UnhandledExceptionEventArgsis set to false.

"Rakesh" <an*******@discussions.microsoft.com> wrote in messagenews:05****************************@phx.gbl...

Hi Jan,

Thanks!

So do u mean that we have to go about the same old way of try-catch in this case? Any other way?

Rakesh

>-----Original Message-----
>No, the unhandled exceptions on other threads wont be

caught.

>
>--
>Greetz,
>Jan
>__________________________________
>Read my weblog: http://weblogs.asp.net/jan
>"Rakesh" <an*******@discussions.microsoft.com> schreef

in bericht

>news:04****************************@phx.gbl...
>> Hi,
>>
>> I am catching unhandled exception by attached an event >> handler on the Application.ThreadException event. This >> will ensure that I could handle all uncaught exceptions >> on the main thread.
>>
>> But, suppose I create a new thread within my app and an >> unhandled exception is generated in that thread, will >> that exception be caught here?
>>
>> Thanks in advance,
>> Rakesh
>>
>
>
>.
>

.

[Rakesh]

It will catch exceptions only in the main thread.

-----Original Message-----
catch (Exception e)
{
}

In the main would catch everything right?
"Rakesh" <an*******@discussions.microsoft.com> wrote in messagenews:05****************************@phx.gbl...

Hi Jan,

Thanks!

So do u mean that we have to go about the same old way of try-catch in this case? Any other way?

Rakesh

>-----Original Message-----
>No, the unhandled exceptions on other threads wont be

caught.

>
>--
>Greetz,
>Jan
>__________________________________
>Read my weblog: http://weblogs.asp.net/jan
>"Rakesh" <an*******@discussions.microsoft.com> schreef

in bericht

>news:04****************************@phx.gbl...
>> Hi,
>>
>> I am catching unhandled exception by attached an event >> handler on the Application.ThreadException event. This >> will ensure that I could handle all uncaught exceptions >> on the main thread.
>>
>> But, suppose I create a new thread within my app and an >> unhandled exception is generated in that thread, will >> that exception be caught here?
>>
>> Thanks in advance,
>> Rakesh
>>
>
>
>.
>

.

[codymanix]

The only way to catch all exceptions in every thread is to enclose every
thread proc in a try/catch clause.

--
cody

[Freeware, Games and Humor]
www.deutronium.de.vu || www.deutronium.tk

Watson :D

How does watson catch UE's? Cant we do something similar?
"Rakesh" <an*******@discussions.microsoft.com> wrote in message
news:05****************************@phx.gbl...

It will catch exceptions only in the main thread.

-----Original Message-----
catch (Exception e)
{
}

In the main would catch everything right?
"Rakesh" <an*******@discussions.microsoft.com> wrote in

message

news:05****************************@phx.gbl...

Hi Jan,

Thanks!

So do u mean that we have to go about the same old way of try-catch in this case? Any other way?

Rakesh

>-----Original Message-----
>No, the unhandled exceptions on other threads wont be
caught.
>
>--
>Greetz,
>Jan
>__________________________________
>Read my weblog: http://weblogs.asp.net/jan
>"Rakesh" <an*******@discussions.microsoft.com> schreef
in bericht
>news:04****************************@phx.gbl...
>> Hi,
>>
>> I am catching unhandled exception by attached an event >> handler on the Application.ThreadException event. This >> will ensure that I could handle all uncaught exceptions >> on the main thread.
>>
>> But, suppose I create a new thread within my app and an >> unhandled exception is generated in that thread, will >> that exception be caught here?
>>
>> Thanks in advance,
>> Rakesh
>>
>
>
>.
>

.

Could have a launcher program that does a process start and catches the
exception there?
<di********@discussion.microsoft.com> wrote in message
news:Oo**************@TK2MSFTNGP12.phx.gbl...

Watson :D

How does watson catch UE's? Cant we do something similar?
"Rakesh" <an*******@discussions.microsoft.com> wrote in message
news:05****************************@phx.gbl...

It will catch exceptions only in the main thread.

-----Original Message-----
catch (Exception e)
{
}

In the main would catch everything right?
"Rakesh" <an*******@discussions.microsoft.com> wrote in

message

news:05****************************@phx.gbl...
> Hi Jan,
>
> Thanks!
>
> So do u mean that we have to go about the same old way

of

> try-catch in this case? Any other way?
>
> Rakesh
>
>
>
> >-----Original Message-----
> >No, the unhandled exceptions on other threads wont be
> caught.
> >
> >--
> >Greetz,
> >Jan
> >__________________________________
> >Read my weblog: http://weblogs.asp.net/jan
> >"Rakesh" <an*******@discussions.microsoft.com> schreef
> in bericht
> >news:04****************************@phx.gbl...
> >> Hi,
> >>
> >> I am catching unhandled exception by attached an

event

> >> handler on the Application.ThreadException event.

This

> >> will ensure that I could handle all uncaught

exceptions

> >> on the main thread.
> >>
> >> But, suppose I create a new thread within my app

and an

> >> unhandled exception is generated in that thread,

will

> >> that exception be caught here?
> >>
> >> Thanks in advance,
> >> Rakesh
> >>
> >
> >
> >.
> >
.

[Jan Tielens]

I think that is what Dave meant. But be awere it's only in the current app
domain!

--
Greetz,
Jan
__________________________________
Read my weblog: http://weblogs.asp.net/jan
"Rakesh" <an*******@discussions.microsoft.com> schreef in bericht
news:02****************************@phx.gbl...

Hi Dave,

I want to know if i got you right:

So if i have only one appdomain and i attach an event
handler in the
AppDomain.CurrentDomain.UnhandledException, will that
ensure that I can handle all the uncaught exceptions
regardless of whichever thread they are in?

Rakesh

-----Original Message-----
You can attach a handler to the

AppDomain.CurrentDomain.UnhandledException

event, but be aware that one of its limitations is that

it will only work

for the default appdomain.

If you create the thread yourself then you should put a

try-catch block

within the thread's start function to ensure that you

will catch and handle

all exceptions. For the main thread and threads that

originate in unmanaged

code, an unhandled exception will terminate the app. For

threads you create

manually, threadpool threads, and finalizer threads,

even though your

unhandled exception handler is called, the runtime will

catch and swallow

all exceptions; the IsTerminating field in the

UnhandledExceptionEventArgs

is set to false.

"Rakesh" <an*******@discussions.microsoft.com> wrote in

message

news:05****************************@phx.gbl...

Hi Jan,

Thanks!

So do u mean that we have to go about the same old way of try-catch in this case? Any other way?

Rakesh

>-----Original Message-----
>No, the unhandled exceptions on other threads wont be
caught.
>
>--
>Greetz,
>Jan
>__________________________________
>Read my weblog: http://weblogs.asp.net/jan
>"Rakesh" <an*******@discussions.microsoft.com> schreef
in bericht
>news:04****************************@phx.gbl...
>> Hi,
>>
>> I am catching unhandled exception by attached an event >> handler on the Application.ThreadException event. This >> will ensure that I could handle all uncaught exceptions >> on the main thread.
>>
>> But, suppose I create a new thread within my app and an >> unhandled exception is generated in that thread, will >> that exception be caught here?
>>
>> Thanks in advance,
>> Rakesh
>>
>
>
>.
>

.

[Bijoy Thulasidharan]

try this
AppDomain.CurrentDomain.UnhandledException += new
UnhandledExceptionEventHandler(Domain_Exception_Ha ndler);

it should handle all the exceptions that occur in the app domain no matter
on which thread.

<di********@discussion.microsoft.com> wrote in message
news:OP**************@TK2MSFTNGP10.phx.gbl...

Could have a launcher program that does a process start and catches the
exception there?
<di********@discussion.microsoft.com> wrote in message
news:Oo**************@TK2MSFTNGP12.phx.gbl...

Watson :D

How does watson catch UE's? Cant we do something similar?
"Rakesh" <an*******@discussions.microsoft.com> wrote in message
news:05****************************@phx.gbl...

It will catch exceptions only in the main thread.
>-----Original Message-----
>catch (Exception e)
>{
>}
>
>In the main would catch everything right?
>
>
>"Rakesh" <an*******@discussions.microsoft.com> wrote in
message
>news:05****************************@phx.gbl...
>> Hi Jan,
>>
>> Thanks!
>>
>> So do u mean that we have to go about the same old way
of
>> try-catch in this case? Any other way?
>>
>> Rakesh
>>
>>
>>
>> >-----Original Message-----
>> >No, the unhandled exceptions on other threads wont be
>> caught.
>> >
>> >--
>> >Greetz,
>> >Jan
>> >__________________________________
>> >Read my weblog: http://weblogs.asp.net/jan
>> >"Rakesh" <an*******@discussions.microsoft.com> schreef
>> in bericht
>> >news:04****************************@phx.gbl...
>> >> Hi,
>> >>
>> >> I am catching unhandled exception by attached an
event
>> >> handler on the Application.ThreadException event.
This
>> >> will ensure that I could handle all uncaught
exceptions
>> >> on the main thread.
>> >>
>> >> But, suppose I create a new thread within my app
and an
>> >> unhandled exception is generated in that thread,
will
>> >> that exception be caught here?
>> >>
>> >> Thanks in advance,
>> >> Rakesh
>> >>
>> >
>> >
>> >.
>> >
>
>
>.
>

[Dave]

You aren't really catching them; think of it as a notification that one
occurred. It gives you an opportunity to provide some application-wide
policies (log it, notify someone via email, terminate the process, etc). If
you want to programmatically recover from it then you must wrap the callsite
throwing the exception in a try-catch block.

If you look at the fields in the UnhandledExceptionEventArgs the unhandled
exception handler gets, one of them is the flag I mentioned called
IsTerminating. This is a read-only property, which means that the runtime
itself is determining what will happen next and that it is too late to
recover from it.

If you hook the AppDomain.CurrentDomain.UnhandledException you will be
notified that the exception occurred but you will not be able to recover
from it within this method. I don't know what functionality you want to
provide so I do not know if this is suitable or not for you.

"Rakesh" <an*******@discussions.microsoft.com> wrote in message
news:02****************************@phx.gbl...

Hi Dave,

I want to know if i got you right:

So if i have only one appdomain and i attach an event
handler in the
AppDomain.CurrentDomain.UnhandledException, will that
ensure that I can handle all the uncaught exceptions
regardless of whichever thread they are in?

Rakesh

-----Original Message-----
You can attach a handler to the

AppDomain.CurrentDomain.UnhandledException

event, but be aware that one of its limitations is that

it will only work

for the default appdomain.

If you create the thread yourself then you should put a

try-catch block

within the thread's start function to ensure that you

will catch and handle

all exceptions. For the main thread and threads that

originate in unmanaged

code, an unhandled exception will terminate the app. For

threads you create

manually, threadpool threads, and finalizer threads,

even though your

unhandled exception handler is called, the runtime will

catch and swallow

all exceptions; the IsTerminating field in the

UnhandledExceptionEventArgs

is set to false.

"Rakesh" <an*******@discussions.microsoft.com> wrote in

message

news:05****************************@phx.gbl...

Hi Jan,

Thanks!

So do u mean that we have to go about the same old way of try-catch in this case? Any other way?

Rakesh

>-----Original Message-----
>No, the unhandled exceptions on other threads wont be
caught.
>
>--
>Greetz,
>Jan
>__________________________________
>Read my weblog: http://weblogs.asp.net/jan
>"Rakesh" <an*******@discussions.microsoft.com> schreef
in bericht
>news:04****************************@phx.gbl...
>> Hi,
>>
>> I am catching unhandled exception by attached an event >> handler on the Application.ThreadException event. This >> will ensure that I could handle all uncaught exceptions >> on the main thread.
>>
>> But, suppose I create a new thread within my app and an >> unhandled exception is generated in that thread, will >> that exception be caught here?
>>
>> Thanks in advance,
>> Rakesh
>>
>
>
>.
>

.