What will happen if web config file has been changed like connection while site running

Question

0.00/5 (No votes)

See more:

What will happen if web config file has been changed like connection while site running how much time it will be taken for affect in site after changed

[edit]SHOUTING removed - OriginalGriff[/edit]

Posted 14-Jul-12 20:35pm

DGKumar

Updated 14-Jul-12 20:36pm

OriginalGriff

v2

Add a Solution

Comments

OriginalGriff 15-Jul-12 2:37am

DON'T SHOUT. Using all capitals is considered shouting on the internet, and rude (using all lower case is considered childish). Use proper capitalisation if you want to be taken seriously.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Yvan Rodrigues · Answer 1 · 2012-07-15T11:49:00

Solution 1

As soon as the file has been modified on disk, IIS will notify the Application Pool to reload it. It is more or less instantaneous. You will notice because the next page reload will be noticibly slower due to recompilation.

Posted 15-Jul-12 11:49am

Yvan Rodrigues

db7uk · Answer 2 · 2012-07-15T12:03:00

Yvan is correct if IIS is set to reload on configuration change. The problem is not limited to just a performance hit because of recompilation. With this you will also loose session, application and other state (if in InProc mode). There is a trick though. If you use configSource attribute to specify a seperate configuration file which can be updated without the app domain refresh.

http://msdn.microsoft.com/en-us/library/ackhksh7.aspx[^]