What is the correct way to ignore ThreadAbortException while logging exceptions?
Is it just safe to hold it in an empty catch block to make it disappear?
If you move the thread abortexation call stack, Thread Reset Abort can call . So try to do something like this:
try {// some code} hold (pre-threaded exposure) {// thread some logging. ResetAbort (); } For "true" - this depends on your usage scenario. I usually take precautions about catching them as long as you understand why it has been raised. It should be done carefully with a "now stop, speed and drop what you are doing" in the escinse, to reset it and proceed further.
Comments
Post a Comment