As with all asp.net applications, a Web.config file is an XML based settings and configuration file for the application.

As well as configuring many asp.net specific settings, the file also contains two connection string definitions, a number of application settings, and configuration for the various Providers used in DotNetNuke.

Whilst the install Package contains a web.config file, some of the other packages do not, which can lead to confusion for new users. There is a good reason for this - DotNetNuke upgrades are performed by copying new files over the existing website, so if a web.config file existed in all packages then it would overwrite the existing web.config file and application specific values would be lost.

If you are using a package such as the upgrade or source package and it does not have a web.config file, you may use one of the other config files in the root folder instead by renaming it. The files are slightly different and intended for different audiences, please read their pages for futher information.

release.config

development.config

Web.Config Sections

AppSettings Section

• SiteSqlServer
  • This is the legacy connection string that was necessary when using .NET 1.0 or 1.1. As of .NET 2.0 (DotNetNuke Core 4.x or greater), this should no longer be used and is a separate section "connectionStrings" in the web.config.
• InstallTemplate
• AutoUpgrade
• UseInstallWizard
• InstallMemberRole
• ShowMissingKeys
• EnableCachePeristence
• HostHeader
• RemoveAngleBrackets
• PeristentCookieTimeOut
• UsePortNumber
  • Preserves the port number if you're using a port number other than 80 (the standard).
• InstallationDate
  • This section is added during the initial installation of DotNetNuke. It will have a value that equals the date of that installation (1/2/2011 for example). When not present (and an install does exist) users could be redirected to the Install.aspx page.