title: WCF Service calling Domain Services - Domain Services reading WCF Service's web.config
body: <p>Recently I encountered a problem with WCF Service and Domain Services communication. The WCF Service calls a method on Domain Services, which then establishes a new database connection. It throws an error - connection cannot be created because the connection string cannot be found.
  Now, the connection string it's looking for is present in the Domain Services' web config file, but doesn't exist in the WCF Service's web config file (so if I add the connection string to the WCF Service web config, it works fine). </p>
  
  <p>Why is it checking the WCF Service web config file for this connection string? What can I do to stop it from doing this and ensure that Domain Services always use its own web.config, regardless of who the client is?</p>