I thought I would put those settings into Cache and then invalidate them if the web.Config file changes. Reading some articles make it seem that this is completely unnecessary.
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.
I thought I would put those settings into Cache and then invalidate them if the web.Config file changes. Reading some articles make it seem that this is completely unnecessary.
The web.config file is already cached in memory. Have a look at this question
this question.
It’s automatically refreshed when the file is touched, too.