title: Using Linq to Sql w/different environments/connection strings
body: <p>Fairly simple question that I can't remember.  We have three environments: Local machine (unique for each developer), Development, and Production.  Connection Strings are in a config file (not web.config, but web.config points to the file); only one is active at a given time (the other two are commented out; all three have the same name but different values for each environment).</p>
  
  <p>I'm using a rudimentary version of the <em>ActiveRecord</em> pattern to handle data access (i.e. static <code>GetByProperty</code> methods in the Linq-generated CS file).  To ensure that all of us can use the Linq classes without having to muck about with the designer, all I would have to do is  pass in that configuration setting with the connection string (e.g. <code>ConfigurationManager.AppSetting["TheConnectionString"]</code>) when I new up the <code>DataContext</code>, correct?  I am going the approach of newing up a context per request; is there any issue (other than DRY, as I'd be repeating the whole connection string every method) I should be aware of passing the connection string in every time, or is that standard operating procedure?</p>