By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,969 Members | 1,522 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,969 IT Pros & Developers. It's quick & easy.

Modified Web.config do I need to restart IIS?

P: 2

I have modified my Web.config file. Will I have to restart IIS inorder for the changes to take effect?

Thank you,
Jun 4 '07 #1
Share this Question
Share on Google+
4 Replies

Expert 5K+
P: 7,872
Mmmmmm if you uploaded the new web.config file you will probably have to restart that individual webservice. Under the IIS management you can start and stop individual webservices.
However, if you don't care, you can restart the whole iis service.

If you upload a file called app_offline.htm (has to be at least 1024 bytes i believe) the IIS service will imedialty shutdown/unload the webservice for the directory where you uploaded the file. Make changes to your web.config. Then you can juse remove the app_offline.htm file and the next call to your webpage will start the service back up with your changes
Jun 4 '07 #2

Expert Mod 5K+
P: 9,731
I've never had to restart my IIS after editing my web.config.
It wouldn't hurt though.
Jun 4 '07 #3

P: 2
Thank you very much for your quick replies.

I had tested my changes without restarting the webservice, but I had restarted my browser and my changes were successful. I am unsure if my browser was running and I did a refresh of the page if my changes would have taken effect. In order to ensure all users are affected by the change I will have the webservice restarted.

Once again, thank you very much for your help.
Jun 4 '07 #4

Expert 100+
P: 663
I use the Web.Config to assign specific permissions to users based on an employee id. The great part of using the Web.Config for this is if I need to add or remove an employee id I do not have to recompile the dll for the change to work on my production servers. Just save the change to the Web.Config and refresh your web page. The change should now be in production.

Jun 4 '07 #5

Post your reply

Sign in to post your reply or Sign up for a free account.