title: Where should connection strings be stored in a n-tier asp.net application
body: <p>Folks,</p>
  
  <p>I have an ASP.NET project which is pretty n-tier, by namespace, but I need to separate into three projects:  Data Layer, Middle Tier and Front End.</p>
  
  <p>I am doing this because... </p>
  
  <p>A) It seems the right thing to do, and</p>
  
  <p>B) I am having all sorts of problems running unit tests for ASP.NET hosted assemblies.</p>
  
  <p>Anyway, my question is, where do you keep your config info?</p>
  
  <p>Right now, for example, my middle tier classes (which uses Linq to SQL) automatically pull their connection string information from the web.config when instantiating a new data context.</p>
  
  <p>If my data layer is in another project can/should it be using the web.config for configuration info?</p>
  
  <p>If so, how will a unit test, (typically in a separate assembly) provide soch configuration info?</p>
  
  <p>Thank you for your time!</p>