title: Do .Net WebService WSDL Complex Types Require Properties to have a Get/Set?
body: <p>I am defining a web service which calls a service library. The service library has an object called customer with a customer ID defined the following way:</p>
  
  <pre><code>public class Customer
  {
      private int _customerID;
      public int CustomerID
      {
          get { return _customerID; }
      }
  }
  </code></pre>
  
  <p>When I try to pass a customer object back through my web service, it seems that the WSDL generated doesn't include the property CustomerID, unless I define a setter. It seems like requiring a setter is undesireable in certain circumstances.  Am I missing something, or does generating a WSDL require a property to have a getter/setter in order to be exposed to the client?</p>