I want to be able to change some app settings programmatically because the settings are unrelated and too few to put in a table. I understand the application will restart unless I set the
restartOnExternalChanges to false. Not sure what would happen on the front end of the site if the app restarts. I'm using an StateServer for the session state. I don't imagine there would be a problem. Not exactly sure though.
Not sure what would happen on the front end of the site if the app restarts. I'm using an StateServer for the session state. I don't imagine there would be a problem. Not exactly sure though.
As far as I know, if you edit the web config, the application pool of the site in IIS will restart (this typically takes a couple of seconds).
As a result the next page request(s) will be slower (since nothing will be cached anymore). In my opinion this is main problem if you config the session state as out-of-process.
If Session state is configured as out-of-process (database or service) then recycling the app pool won't lose any session state.
Member
12 Points
81 Posts
Writing To Web.config <AppSettings>
May 12, 2018 01:35 AM|oneillj|LINK
I want to be able to change some app settings programmatically because the settings are unrelated and too few to put in a table. I understand the application will restart unless I set the restartOnExternalChanges to false. Not sure what would happen on the front end of the site if the app restarts. I'm using an StateServer for the session state. I don't imagine there would be a problem. Not exactly sure though.
Jim
Star
8931 Points
2722 Posts
Re: Writing To Web.config <AppSettings>
May 14, 2018 02:54 AM|Brando ZWZ|LINK
Hi oneillj,
As far as I know, if you edit the web config, the application pool of the site in IIS will restart (this typically takes a couple of seconds).
As a result the next page request(s) will be slower (since nothing will be cached anymore). In my opinion this is main problem if you config the session state as out-of-process.
If Session state is configured as out-of-process (database or service) then recycling the app pool won't lose any session state.
Best Regards,
Brando