I read this on the ASPDNSF ML/DNN forums from Joe Brinkman.

A properly performed upgrade should not overwrite your web.config file.  In version 4.7 we added the ability to merge any needed web.config changes.  Even in older versions we never include a web.config file in the upgrade package.  If upgrading from a version prior to 4.7, then you should manually merge any web.config changes.

I hate to sound like a Newbie since I have been with DNN since v 1 but I was not aware that the changes to the web.config were automated. So are you saying if I go to upgrade a DNN site to 4.9.1 that I don't have to copy the release.config, rename it to web.config and make changes the connection, machinekey, etc? Is this all automated? Do I just copy the upgrade files into the site and run the upgrade and it updates any changes necessary to the web.config

If so, that would sure save me a lot of time as I have about 75 DNN installs.

This may just be a Yes or No answer, but if there is a blog entry or something on the DNN site that you could point me to for more info that would be great.

Cliff
 

and also this:

http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/1843/Core-members-feel-the-pain-of-upgrades-too.aspx

Cliff.. you really must read our blogs better :)

DNN Blog | Twitter: @erikvb | LinkedIn:

Search for "xmlmerge" or even "merge" on the blogs page.