title: Problems with Web.config and App.config
body: <h2>Intro:</h2>
  
  <ul>
  <li>Normally we store <code>ConnectionStrings</code> and some other settings (<code>&lt;appSettings&gt; &lt;add key...</code>) in the <code>Web.config</code> or <code>App.config</code>. </li>
  </ul>
  
  <h2>My scenery:</h2>
  
  <ul>
  <li><p>Web application using factory pattern
  with direct injection to read data
  providers.</p></li>
  <li><p>In the <code>web.config</code> I have the key
  that tells me which DLL (provider)
  will I use to retrieve my data. </p></li>
  <li><p>I can have more than one provider
  (each DLL will be a provider for MS
  SQL, MySQL, or get the data from
  some SOA service).</p></li>
  <li><p>Each DLL has his own name (ID and namespaces) and will need to have is own
  configurations (dataconnections,
  service urls, etc...) , the first
  idea is to write then in the
  <code>app.config</code>.</p></li>
  </ul>
  
  <h2>Problems:</h2>
  
  <ul>
  <li><p><strong>#1</strong> - The website is running (runtime) I need to change the Data Provider, <strong>how can I do this?</strong> Somehow the default value written in the <code>Web.config</code> will be changed.</p>
  
  <ul>
  <li>My objective is to be able to have multiple providers (and during runtime: add/delete providers and change configurations) - this leads me to my second problem:</li>
  </ul>
  
  <p>.</p></li>
  <li><p><strong>#2</strong> - Each Data Provider has custom configurations and App.Config files do not work with dll assemblies, only executables. This means that I need to write then on my Web.Config (I do not like this option, because once again I am updating my web.config in runtime). <strong>how can I solve this?</strong></p>
  
  <ul>
  <li>I am trying to avoid to write a custom settings XML file. My ideal solution is to deploy somehow the <code>DLL</code> and <code>DLL.config</code> per each provider. And once again during runtime I may need to change this configuration values.</li>
  </ul></li>
  </ul>
  
  <p>.</p>