Is there any valid reason why a
catch block on a lower layer would throw back an exception caused by a higher, unknown layer using the following syntax:
... rather than:
In the first case, not only the
catch block doesn't deal with the exception, but it also reset its
StackTrace property, making it more difficult to understand what caused it.
Why would anyone want a
catch block in a lower layer to behave like this?