title: Version-control: svcmap, disco, xsd, wsdl, svcinfo and datasource files
body: <p>We have a webservice named, let's say Foo.</p>
  
  <p>So there is a Foo.svc file and a code behind Foo.svc.cs.</p>
  
  <p>We add a silverlight project and wish to use the Foo.svc services so we add a Service Reference and call it's namespace FooBar.</p>
  
  <p>This creates the following files :</p>
  
  <ul>
  <li>Reference.cs</li>
  <li>Reference.svcmap</li>
  <li>Foo.xsd</li>
  <li>Foo.disco</li>
  <li>configuration.svcinfo</li>
  <li>Foo.wsdl</li>
  <li>Also various *.datasource files.</li>
  </ul>
  
  <p>Over time we update the Foo.svc and add more Web Services (methods and interfaces) and the number of files in the FooBar directory is growing.</p>
  
  <p>I have 26 Foo(nn).xsd files in this directory - where nn = 1 to 26. </p>
  
  <p>My configuration.svcinfo is upto configuration91.svcinfo.</p>
  
  <p>My question is this? Do any of these files need to be version controlled? Can they all be deleted each time you do a build \ deploy (as long as you do an update service reference)?</p>