title: How to use 2 different connection strings in a single project?
body: <p>We have a scenario where we have two SQL Server databases, one for testing and one for deployment. When I came onto the project, they had been using typed datasets and passing the connection string to determine which database. There was only one typed dataset for both.</p>
  
  <p>Now, I am trying to do this with Entity Framework. While I could have two EDMX models in the same Class Library, the catch is both databases have the same tables, therefore generate the same C# classes with the same names and there is collisions.</p>
  
  <p>Is there anyway to deal with this scenario?</p>