0

When creating a webapplication we get a web.config file, if we edit this config file the webapplication will restart.

There is a way to reference another config file in .NET but will this solve the problem?

<appSettings configSource="Config\AppSettings.config"/>
  1. If I change and save the AppSettings.config, will the service continue to run without stop?
  2. How will we get the configurations located in AppSEttings.config from within the code?
  3. If we ask after a specific setting located in AppSettings.config 1000 times in 1 sec, will .NET read the file every time or will to use some kind of cache? And if so listen on changes in AppSettings.config file to do a clear of this cache?
Banshee
  • 15,376
  • 38
  • 128
  • 219
  • I think all as been said in these other questions: http://stackoverflow.com/questions/719928/how-do-you-modify-the-web-config-appsettings-at-runtime and http://stackoverflow.com/questions/1254677/change-in-appsettings-needs-restart-my-application-how-can-i-avoid – Simon Mourier May 30 '14 at 07:27

3 Answers3

1

The appSettings key supports two attributes for external configuration: file and configSource (inherited)

<appSettings file="AppSettings.config" />
<appSettings configSource="AppSettings.config" />

In both cases changing the external file does not restart the worker process, see http://msdn.microsoft.com/en-us/library/ms228154(v=vs.100).aspx and http://msdn.microsoft.com/en-us/library/system.configuration.sectioninformation.configsource.aspx (for configSource there is a RestartOnExternalChanges property that forces a restart on change)

Read more at Changing AppSetting does not have effect on Application and Is web.config or app.config cached in memory

To access the settings use 

WebConfigurationManager.AppSettings["key_name"]
Community
  • 1
  • 1
user2316116
  • 6,726
  • 1
  • 21
  • 35
0

1) if you phsically change web.config then service will restart, but if you change programmatically then it will not restart, so you needn't have another web.config, you can do it programmatically. 2) You can read here 3) It is cached, read one time in application start event

kemals
  • 216
  • 1
  • 7
0

Consider storing (some) settings in a database instead of web.config.

Reg Edit
  • 6,719
  • 1
  • 35
  • 46