title: Why should I use Visual Studio service references over svcutil?
body: <p>So it seems like I have a couple of major options when getting WCF service proxy code into a project in Visual Studio:</p>
  
  <ol>
  <li><p>Use <strong>Visual Studio's built-in tooling</strong> for <a href="http://www.eggheadcafe.com/tutorials/aspnet/a1647f10-9aa4-4b0c-bbd9-dfa51a9fab8e/adding-wcf-service-references.aspx">Service References</a></p></li>
  <li><p>Use a <strong>simple svcutil command</strong>, something like <code>svcutil http://[my
  endpoint] /namespace:[my namespace] /noconfig</code> (since I use some
  fairly standard bindings across projects), and drag the resulting
  file into my project (or upgrade in place).</p></li>
  </ol>
  
  <p>To be clear, <strong>option 2 feels like the best one</strong>, albiet with no built-in tooling for updating.  But the Service Reference dialog generates like a zillion files.  <strong>Is there any obscure benefit to VS Service References that I'm missing?</strong></p>