title: Throwing nested Exceptions from a catch block...is this wise?
body: <p>I want to implement custom exception handling in my library so that I know where an exception occurred, so I am doing this:</p>
  
  <pre><code>try
  {
      DoSomething();
  }
  catch(Exception ex)
  {
      //LibraryException refers to any exception in the libraries exception hierarchy
      throw new LibraryException(ex.Message, ex);
  }
  </code></pre>
  
  <ul>
  <li><p>Should this be avoided? </p></li>
  <li><p>Does it have any performance implications?</p></li>
  <li><p>What are the implications of catching, nesting and re-throwing exceptions?</p></li>
  </ul>