title: How to trace WCF serialization issues / exceptions
body: <p>I occasionally run into the problem that an application exception is thrown during the WCF-serialization (after returning a DataContract from my OperationContract). The only (and less meaningfull) message I get is</p>
  
  <blockquote>
    <p>System.ServiceModel.CommunicationException
    : The underlying connection was
    closed: The connection was closed
    unexpectedly.</p>
  </blockquote>
  
  <p>without any insight to the inner exception, which makes it really hard to find out what caused the error during serialization.</p>
  
  <p>Does someone know a good way how you can trace, log and debug these exceptions? Or even better can I catch the exception, handle them and send a defined FaulMessage to the client?</p>
  
  <p>thank you</p>