In IIS7, why w3wp is not reset after web.config is amended? I observed the memoory remains the same.
Thanks.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In IIS7, why w3wp is not reset after web.config is amended? I observed the memoory remains the same.
Thanks.
When you modify web.config it’s the AppDomain hosted in the
w3wpprocess which is unloaded. This doesn’t mean that the memory should change. Also there’s the auto start feature in IIS 7.5 and ASP.NET 4.0 which could load it once again to avoid cold starts.