Updating web.config on upgrades

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This thread is closed to new posts. You must sign in to post in the forums.

9/2/2013 8:06:09 AM

crippsy

Total Posts 167

View Posts

Updating web.config on upgrades

Anyone got any hints or tips on managing the web.config file in upgrades.

When we make an upgrade the web.config gets overwritten by the new version. Most bespoke (or addkey ) changes made to the system should be stored in the user.config so that this can surpass web.config and make upgrades simple.

However as far as I have seen, this applies just to "add key" in the "<appSetting file="user.config" section in user.config

On upgrades do we always have to make changes in web.config to other sections such as in "<location> for to set machineKey.config

or to areas in globalisation for culture to be set as auto:en-GB

or to the modules and handler sections for their bespoke changes.

Do these setting have to be applied to web.config on each upgrade or can we add them to user.config, and if so how?

Any thoughts

9/2/2013 9:38:39 AM

Joe Audette

Total Posts 18439

View Posts

Re: Updating web.config on upgrades

Hi,

If you need custom <location and/or handlers, modules etc the only place they can be maintained is in web.config, so yes you must update those items on each upgrade, there is no other way. Machinekey must also be maintained in Web.config. The ONLY thing that can go in user.config is <appSettings.

However, you should not touch the globalization section, instead you should force the language in user.config as specified in Forcing a Specific Language. So that is one less thing to remember.

I suggest create a document that lists each item the you do customize on upgrades so that you have a guide to remind you of the needed changes.

Hope that helps,

Joe

9/4/2013 3:42:29 AM

crippsy

Total Posts 167

View Posts

Re: Updating web.config on upgrades

Many thanks, just as I thought.

A simple reminder to update parts of the web.config is no real issue at all.

Cheers

You must sign in to post in the forums. This thread is closed to new posts.