multiple webconfiguration,modify frequently

Question

1.00/5 (2 votes)

See more:

Hello

Do change the webconfig file frequent run-time, create a problem?

1-If the webconfig file with a large number of key / value be long,do put the key / value in two webconfig files is better or in a file?
2-do put the key is the short amount in webconfig file or in database.
I appreciate tips Here
Thank you in advance

Posted 9-Jul-15 22:52pm

NewWebDesigner

Updated 11-Jul-15 7:24am

v2

Add a Solution

Comments

Afzaal Ahmad Zeeshan 10-Jul-15 5:28am

Why do you want to do this in the first place, I suggest that you don't do this!

Suvendu Shekhar Giri 10-Jul-15 8:33am

Based on your application, you may keep key/values in a separate table with simple design or you can keep a separate config file for this. Don't update web.config frequently.

Dave Kreskowiak 11-Jul-15 14:42pm

Yes!! Start resing these[^]

1 solution

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)

Dave Kreskowiak · Accepted Answer · 2015-07-11T07:13:00

Data that changes frequently should never be put in web.config.

By default, changing web.config causes IIS to restart your web application. Depending on what your app does and whatever libraries you're using, if any, this will cause the next request to be delayed, possibly taking for longer than a client is willing to wait.

If you've got a lot of key/value pairs in your web.config, you made a rather bone-headed move. That kind of data should have been put in some kind of separate database/datastore without even questioning it.