Thanks, although I think that just due to the nature of Thread.Abort() it does still cause issues.
To be a bit clearer, the problem is showing itself only when the the thread is re allocated, and not when it is aborted. It seems that once you abort, the system works fine, and then when a new thread is needed and the framework allocates one a 'random' exception is thrown. I just cant find a clean way of killing a thread as instantly as possible (BackgroundWorker CancelPending is just not responsive enough).
Main Topics
Browse All Topics





by: taliesin1977Posted on 2009-03-25 at 13:49:21ID: 23984537
I am not sure if this is a problem for .NET 2.0 and later. It sounds like for .NET 2.0 and later the ThreadAbortException is delayed until the end of a finally block if it occurs in the finally block.
/archive/2 004/03/15/ 736.aspx
See the comment by cbeyls at the end of this page:
http://dotnet.org.za/ernst