title: Multiple endpoints for single contract in WAS-hosted WCF service?
body: <p>If one needs to expose multiple endpoints (e.g., one with basicHttpBinding, and another with netTcpBinding) for a single contract in a heterogeneous environment, on a WAS-hosted service, how does one do it?</p>
  
  <p>Everything I've read about WAS configuration of endpoints indicates that endpoint addresses and host base addresses should be left blank, because WAS is supposed to automatically resolve addresses via the path to the .svc file and the protocol.  </p>
  
  <p>However, it seems impossible to define an HTTP endpoint and a TCP endpoint for the same contract without explicating the addresses.  Every attempt of mine thus far has netted me the coveted "a binding instance has already been associated to listen uri" error.  </p>
  
  <p>Ideas?</p>
  
  <p>Thanks</p>