Re: Thread.Abort
- From: "Willy Denoyette [MVP]" <willy.denoyette@xxxxxxxxxx>
- Date: Wed, 17 Aug 2005 10:44:04 +0200
"Christoph Nahr" <christoph.nahr@xxxxxxxxxxxxx> wrote in message
news:dnm5g1pm224c3tdaalcups74p4hiq33rgv@xxxxxxxxxx
> Or upgrade to .NET Framework 2.0 where this issue has been fixed!
>
> On Tue, 16 Aug 2005 17:27:27 +0200, "Willy Denoyette [MVP]"
> <willy.denoyette@xxxxxxxxxx> wrote:
>
>>Thread.Abort() is a method you should only call to abort the current
>>thread,
>>the only valid reason to call it on another thread is when you intend to
>>unload the application domain anyway.
>>There are numerous things that can go wrong when aborting another thread,
>>Please search the archives, this has been discussed several times before
>>in
>>this and other NG's.
>>
>>Willy.
> --
> http://www.kynosarges.de
True, but I don't believe all issues are fixed, as far as I know
Thread.Abort() will no longer be injected while running exception handling
code blocks, but will be delayed until catch/finally blocks exit, but the
issues remain when executing outside try/catch/finally blocks.
Willy.
.
- Follow-Ups:
- Re: Thread.Abort
- From: Christoph Nahr
- Re: Thread.Abort
- References:
- Thread.Abort
- From: Urs Vogel
- Re: Thread.Abort
- From: Willy Denoyette [MVP]
- Re: Thread.Abort
- From: Christoph Nahr
- Thread.Abort
- Prev by Date: Looking for a decent data access architecture to implement
- Next by Date: RE: Single instance of an object between different processes?
- Previous by thread: Re: Thread.Abort
- Next by thread: Re: Thread.Abort
- Index(es):
Relevant Pages
|