title: Can I remove empty catch with throw?
body: <p>I'm hoping this is straightforward.  I work on a large code-base, the overall quality is good, but occasionally you get some of these:</p>
  
  <pre><code>try
  {
     // Calls a .NET remoting method.
  }
  catch
  {
     throw;
  }
  </code></pre>
  
  <p>Note there is no finally logic and the catch does not specify any exceptions or do anything other than what I've provided above.  However, I know that catching and re-throwing can alter the call-stack in the exception details.  What I'm not sure about is if this behaviour is here specifically because of a .NET remoting call.</p>
  
  <p>Is it safe to remove this try-catch?  So far as I can see, it is, but I thought I'd double check for any odd behaviour first.</p>