0

I search about put large amounts of key / value in the web config and change it frequently. The result was that, frequently changing web configuration is not good.do create two web.config ,one for settings and the other for key/value is better? What is proposed instead? Is there a limit to the size of the web.config?

farid bekran
  • 2,684
  • 2
  • 16
  • 29
user122121212
  • 40
  • 7
  • 1
    Every time you change your `web.config` and save it, the app pool your web application is running in is recycled - really *not* a good idea! Put your settings that change frequently into a separate config file, or store them in the database or something – marc_s Jul 12 '15 at 07:19
  • ok,when i put key/value in a separate file and have frequently change and setting in the other by not frequently change,is there any setting to not restart whole app when one webconfig change? – user122121212 Jul 12 '15 at 07:46
  • When `web.config` changes - the app pool restarts - there's nothing you can do about that. Period. So if you want to avoid this - **do not** constantly modify `web.config` - put those settings elsewhere – marc_s Jul 12 '15 at 08:07
  • so,when i change webconfig files,setting or key/value app restart and can not set no restart!if i want no restart put in database or other.ok? – user122121212 Jul 12 '15 at 08:40
  • see this: http://stackoverflow.com/a/2232097/1095390 – farid bekran Jul 12 '15 at 10:13

0 Answers0