title: Bind a connectionString to every DataProvider constructor OR inject a connection interface
body: <p>My Services are all accessing DataProvider classes. Each DataProvider constructor gets the connectionString as parameter injected with a DI tool.</p>
  
  <p>Where is the advantage of hiding the connectionString in a IConnectionString interface and inject this interface instead of the connectionString?</p>
  
  <p>Just consider for your answer: I do not use any interface to access my DataProvider classes. And these classes do not use IDbConnection.</p>
  
  <p>I completely tie myself to the MS SQL Server and this is what I want :)</p>