Hi Barry,

The best way to do this is to build some check logic into your thread loop.
At the beginning of the loop have it check some condition

while(.t.)
{
   if (this.Cancelled)
       exit;

   ... do your thread processing
}

Then your main thread code can set this flag in some way and cause the
thread to exit.

As to your blocking Socket call there's no way to deal with that other than
to possibly use an Async Delegate and check the delegate for completion. The
advantgate there is that your thread loop can stay active and wait for
completion as well as also check for cancellation requests. But this means
you will use yet another thread to actually process the socket.

+++ Rick ---

Use a Flag to indicate to the thread that the app is about to exit and if
the flag is set simply return from the thread proc.

if you have a thread waiting inifite time for networkpackets or similar,
you should define it as a backgroundthread anyways.

Or even better, use a thread from the ThreadPool, those get always
destroyed when the last foreground thread of your app terminates.

greets
Peter

Hi Barry,

Thread.Abort will work.
It doesn't work when thread is within unmanaged call.

.Close() the socket from your main thread, that will cause a InvalidOperationException from the blocking Read-call on the socket. You need to catch that exception and hide it or do something appropriate for your application
Thread.Abort will as you say not work, since the socket read call is unmanaged.