title: What's the right approach to storing application configuration parameters in an ASP.NET Application?
body: <p>We have lot of application parameters for each module in a C# .NET 4 ASP website.</p>
  
  <p>parameter examples: timeouts, formulae constants, thread limits per module, $ charges per usage etc.</p>
  
  <p>What is best out of following approaches we know:</p>
  
  <ol>
  <li>Use DB config table</li>
  <li>Use an xml. load that xml into local cache on start (and on xml change)</li>
  <li>simple constants.cs file with public const int XYZ = 123; type of key-value pairs.</li>
  <li>web.config (though i think its mostly for deployment type of config)</li>
  <li>Any other way ?</li>
  </ol>
  
  <p>Help on pros and cons and std. approach followed would be helpful.</p>