Some basic questions regarding Thread.Abort() and remoting.
If Thread.Abort() is called on a client thread while that thread is calling
a remote object, it seems that the ThreadAbortException is not thrown until
the remote method call returns. It seems that the Thread.Abort() signal does
not propagate across the remoting boundary. Can someone confirm this
behavior? Is there any additional available documentation about this issue?
Indeed it seems similar to the way Thread.Abort() works across the boundary
between managed and unmanaged code. If Thread.Abort() is called on a thread
that is waiting on a call to unmanaged code, like a call to a COM component,
again the ThreadAbortException is not thrown until the method returns from
the call to unmanaged code.
We are aware of other thread limitations as per the article:
How To Stop a Thread in .NET (and Why Thread.Abort is Evil)
Just wondering if there was any additional information about Thread.Abort()
limitations with regards to remoting.