DNN Platform Suggested Upgrade Path
Following is the recommended upgrade path for DNN Platform based on the experiences of many DNN Community members.
Warning
While the below has been tested and used successfully, there are no guarantees. Each upgrade scenario can result in unique complexities and challenges. Therefore, each upgrade should be treated with full context in mind. For common best practices, please use these basic upgrade steps to provide guidance.
The below is, of course, subject to change. If your current version of DNN Platform is between any of the versions listed below, first upgrade to the closest listed version. For instance, if you are starting with version 09.02.00, you should upgrade first to version 09.03.02.
| FROM Version | TO Version | Notes |
|---|---|---|
| 10.02.01 | 10.02.03 | DNN 10.2.0 introduced a new simplified upgrade process, see Post-10.2.0 Upgrade Guide. DNN 10.2.3 has an issue with uploading upgrades, if upgrading from 10.2.3, please upload your next version package to App_Data\Upgrade folder manually. |
| 09.13.09 | 10.02.01 | DNN 10.0.0 is a significant release with both Breaking Changes and New Features, it also introduced minimum requirements for ASP.NET 4.8 and SQL Server 2017. In addition, it will force-remove DNN-Provided Telerik versions. DNN 10.1.1 new installs use SHA256 as the default password hashing algorithm. This only affects new installs, if you want to migrate an upgraded site to SHA256, please read the documentation for membership provider changes. |
| 09.03.02 | 09.13.09 | DNN 9.4.0 introduced a minimum requirement of ASP.NET 4.7.2. DNN 9.8.0 (and above for the 9.x series releases) brings the OPTIONAL (but HIGHLY RECOMMENDED) Telerik Removal. |
| 09.01.01 | 09.03.02 | DNN 9.2.0 multiple APIs were removed that were marked deprecated in DNN 7 and before. Most of the core modules have been updated since and you can find them at dnncommunity. If you have other modules installed, please check for updates before upgrading to DNN 9.2.0 or later. |
| 08.00.04 | 09.01.01 | |
| 07.04.02 | 08.00.04 | |
| 06.02.08 | 07.04.02 | DNN 7.0.0 has some additional changed pre-requisites, please see the DNN 7 Developer Quick Start for further details. |
| 05.06.08 | 06.02.08 | |
| 05.04.04 | 05.06.08 | |
| 04.09.05 | 05.04.04 | DotNetNuke 5.2.0 introduced the requirement for SQL 2005 and ASP.NET 3.5 SP1. DNN 5.3.0 upgrading from before 5.3.0 to after 5.3.0, you may encounter this error during the upgrade: "Type 'Web.HttpResponse' is not defined." This primarily occurs if the XML module is already installed. To prevent this, check PRIOR to upgrading if the XML module is installed. If so, upgrade it PRIOR to upgrading DotNetNuke to version 4.3.5, available at DNN.XML Module on GitHub. |
| 04.06.02 | 04.09.05 | |
| 04.04.01 | 04.06.02 | DotNetNuke 4.6.2 prior to 4.6.2 site admins had to manually merge key fields in web.config such as the machinekey and both connection strings. With 4.6.2 DotNetNuke introduced functionality known as xmlmerge which automatically does the web.config merging on your behalf. |
| 04.03.07 | 04.04.01 | |
| 03.02.02 | 04.03.07 | Bumped ASP.NET to 2.0, also see Upgrade to DotNetNuke 4.x chapter. This blog post also contains information about upgrading from 3.2.2. to 4.x: Preparing for an upgrade |
| 03.01.01 | 03.02.02 | |
| 02.01.02 | 03.01.01 | |
| 02.00.04 | 02.01.02 |
Note
If you are in a situation where you are unable to make the 09.13.09 -> 10.x upgrade, there is a hot-fix release 09.13.10. This was a special release that contains security patches through the DNN 10.02.00 release and can be used during periods when a 10.x upgrade is not yet possible. For a successful upgrade, it is NOT necessary to stop at 09.13.10 prior to upgrading to 10.x. There is NO guarantee that any future 9.13.x releases will be made, therefore it is suggested to try to prepare for a 10.x upgrade as soon as practical.
Note
If upgrading from DNN 10.02.x and later, it is strongly recommended to follow the new upgrade process outlined in the Post-10.2.0 Upgrade Guide