Have you been hunting for the web.config file in the latest versions of DotNetNuke and been wondering where has it gone?

It's called release.config so that you don't accidentally overwrite your old web.config file if you are upgrading your installation of DotNetNuke.

Make sure you follow the instructions closely and copy across the appropriate elements from your old web.config file to the new release.config file if you are upgrading

Otherwise, simply rename the release.config file to web.config and there you go!

I judt dowenloaded the install for DNN 4.3.2 and found both release.config and web.config in the unzipped files.  Should I delete web.config and then rename release.config and then install?  I found Mr. Walker's installation instructions on another website and he says to rename release.config to web.config after installation.  But once again, Solution Explorer in VS 2005 lists both release.config and web.config.

Thanks for your help.

Buddy

Hello,

They are both the same files, this may be an oversight by the DNN team. -The release.config file was named as such so that you didn't accidentally overwrite your original web.config file when upgrading as you need to transfer across some settings from your old installations web.config file to the new release.config file. (In order to prevent users accidentally overwriting their web.config file - which happened a lot, the DNN team just placed a release.config file in the DNN files which you rename to web.config file once you have transferred across your settings.)

So, they are both the same. - If you are installing a fresh installation then just use the web.config file.

If you are upgrading then make sure you copy across the settings that are required.

Lee:

Thanks for the clarification.

Buddy

I'm not sure if I understand this answer. If as you mentioned release.config and web.config are the same files, as you mentioned, why should we rename the release.config file to web.config instead of simply deleting the release.config file (again assuming they are the same file). If we are doing a fresh installation, should we do just that, delete the release.config? Thanks ahead

Altein

The required contents of web.config change from version to version in DotNetNuke. So, if you're upgrading from one release to another, renaming release.config to web.config won't work.

Here's the process that I use:

1. COPY (not rename) release.config to web-new.config
2. Copy the old connection strings, machine keys, and other necessary changes from the existing web.config to web-new.config
3. RENAME web.config to web-old.config. Sometimes I'll add a date: web-old-20070707.config
4. COPY web-new.config to web.config

Then test your system ...

I need to know where this file resides also. You didn't answer as to the location whether it is the web.config or release.config. My site is a fresh install hosted by PowerDNN and it is timing out on uploading my new skins. I was told I needed to adjust timout settings in the webconfig file. I can't do that if I don't know where it is.

Please help
Jeffrey

Web.config is in the root directory.