Killing a thread

1) Why does the top level try catch get involved at all when it is caught
locally?
Thread.Abort() throws a ThreadAbortException. According to its
documentation

"ThreadAbortException is a special exception that can be caught, but
it will automatically be raised again at the end of the catch block."

You can't both terminate a thread and still execute code on it.

It seems that setting it to nothing accomplishes the same thing.

Using VS 2003, VB, MSDE...

I am stoping a thread with the following code:
Try
Thread.CurrentThread.Abort()

Catch ex As Exception

MessageBox.Show(ex.ToString)

End Try

The MessagBox shows, but then after the End Try it traverses the call stack all the way to the top (same thread) and the exception is caught again by a Try/Catch that is around everthing that happens in this thread.

1) Why does the top level try catch get involved at all when it is caught
locally?

2) I don't really want to thow an exception, I just want to kill the thread. It seems that setting it to nothing accomplishes the same thing. Is there
any disadvantage to doing it this way?

Thanks!
Bobg

Well, then, is ther any way to kill a thread other that .Abort? Without
throwing an exception?

Thanks
Bob Day

"Bob Day" <Bo****@TouchTalk.net> wrote in message
news:OL****************@tk2msftngp13.phx.gbl...

Using VS 2003, VB, MSDE...

I am stoping a thread with the following code:
Try
Thread.CurrentThread.Abort()

Catch ex As Exception

MessageBox.Show(ex.ToString)

End Try

The MessagBox shows, but then after the End Try it traverses the call stack

all the way to the top (same thread) and the exception is caught again by a

Try/Catch that is around everthing that happens in this thread.

1) Why does the top level try catch get involved at all when it is

caught locally?

2) I don't really want to thow an exception, I just want to kill the

thread.

It seems that setting it to nothing accomplishes the same thing. Is there any disadvantage to doing it this way?

Thanks!
Bobg