title: Why would a WCF Contract include a ref/out parameter?
body: <p>I was looking at someone else's WCF service contract and noticed it was using an out parameter:</p>
  
  <pre><code>client.SomeMethod(parameter1, parameter2, out someOutParameter);
  </code></pre>
  
  <p>Is there a good reason for having an out parameter instead of adding it to the response?</p>
  
  <p><strong>edit</strong><br>
  This is what the proxy generated:</p>
  
  <pre><code>public string CreateItem(string contract, string note, out string warning)
  </code></pre>
  
  <p>Now if they needed to return a string and also have a warning, I have usually seen it like this:</p>
  
  <pre><code>public class CreateItemResponse
  {
      public string Result { get; set; }
      public string Warning { get; set; }
  }
  </code></pre>
  
  <p>I was just curious if there was a good reason for not doing it this way, and doing it with a string being returned and a string as an out parameter.</p>