Not sure but I believe it has to do with caller notification. If the thread
aborted, the caller couldn't possibly know what killed the thread. An
automatic rethrow allows the caller to know, since the caller isn't
necessarily the one inducing the thread abort.

Signature
Regards,
Alvin Bruney - ASP.NET MVP
[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
> Hi,
>
[quoted text clipped - 4 lines]
> Thanks in advance
> -Vivek
Vivek - 09 Jul 2005 17:25 GMT
Thanks for your views.
Now that i think more about it I wonder if it has anything to do with giving
functions upper in the call stack a chance to free unmanaged resourecs on
their call stack if any!
Example
foo1 is a method that the thread is executing (basically foo1 is the
ThreadStart parameter)
foo1 calls foo2 . foo2 opens some files (unmanaged calls) and then calls foo3
Assume we call the Abort method while foo3 is executing
If execution concluded in the ThreadAbortException of foo3 the files would
still be open!
Maybe that's the reason by ThreadAbortException is always rethrown unless
ResetAbort is explicitly called?
Any thoughts?
> Not sure but I believe it has to do with caller notification. If the thread
> aborted, the caller couldn't possibly know what killed the thread. An
[quoted text clipped - 9 lines]
> > Thanks in advance
> > -Vivek
Alvin Bruney [MVP - ASP.NET] - 09 Jul 2005 19:07 GMT
that's possible as well. i suspect there are more reasons as well.

Signature
Regards,
Alvin Bruney - ASP.NET MVP
[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
> Thanks for your views.
> Now that i think more about it I wonder if it has anything to do with
[quoted text clipped - 30 lines]
>> > Thanks in advance
>> > -Vivek