title: Throwing a FaultException<T> from a WCF services causes 'The creator of this fault did not specify a Reason.'
body: <p>When throwing a <code>FaultException&lt;CustomFault&gt;</code> like this:</p>
  
  <pre><code>throw new FaultException&lt;CustomFault&gt;(new CustomFault("Custom fault message"));
  </code></pre>
  
  <p>I get the following: "The creator of this fault did not specify a Reason."
  Now according to <a href="http://msdn.microsoft.com/en-us/library/ms576199.aspx" rel="noreferrer">this MSDN article</a> one isn't required to use the <code>FaultReason</code></p>
  
  <p>I have the following Service Contract:</p>
  
  <pre><code>[OperationContract]
  [FaultContract(typeof(CustomFault))]
  CustomType[] SomeMethod(int someParameter);
  
  [DataContract]
  public class CustomFault
  {
      private string report;
  
      public CustomFault(string message)
      {
          this.report = message;
      }
  
      [DataMember]
      public string Message
      {
          get { return this.report; }
          set { this.report = value; }
      }
  }
  </code></pre>
  
  <p>There is a comment on the MSDN article that suggest it is mandatory to use the other <code>FaultReason</code>, but in several other places I have seen people arguing that you shouldn't use the <code>FaultReason</code> unless necessary. </p>
  
  <p>So my question is as follows; is it really mandatory to use the <code>FaultReason</code> and if not - how can i prevent the exception raised when trying to throw a <code>FaultException</code>?</p>
  
  <p><strong>EDIT</strong></p>
  
  <p>By running the sample project from <a href="http://msdn.microsoft.com/en-us/library/ee942778.aspx" rel="noreferrer">this article</a> I get the excact same behavior. Maybe it's caused by an update in .NET an the documentation/samples not being updated.</p>