You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Simplified the ugprades table
This creates a list of links to include in the table so that it improves its readability in markdown.
Then with more space to manage, I inlined the Notes into the table instead of having to scroll down to see the notes.
* Update upgrade notes for DNN 10.2.3 to include manual upload instructions
Copy file name to clipboardExpand all lines: content/getting-started/setup/upgrades/suggested-upgrade-path/index.md
+47-38Lines changed: 47 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,47 +13,56 @@ Following is the recommended upgrade path for **DNN Platform** based on the expe
13
13
14
14
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.
|[10.02.01]|[10.02.03]| DNN 10.2.0 introduced a new simplified upgrade process, see [Post-10.2.0 Upgrade Guide](xref:setup-upgrades-post-10.2.0). <br/> 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.|
19
+
|[09.13.09]|[10.02.01]| DNN 10.0.0 is a significant release with both [Breaking Changes and New Features][bc-10], it also introduced minimum requirements for ASP.NET 4.8 and SQL Server 2017. In addition, it will force-remove DNN-Provided Telerik versions. <br/> 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](xref:security-membership-providers). |
20
+
|[09.03.02]|[09.13.09]| DNN 9.4.0 introduced a minimum requirement of ASP.NET 4.7.2. <br/> DNN 9.8.0 (and above for the 9.x series releases) brings the OPTIONAL (but HIGHLY RECOMMENDED) [Telerik Removal](xref:setup-telerik-removal). |
21
+
|[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][dnncommunity-gh]. <br/> If you have other modules installed, please check for updates before upgrading to DNN 9.2.0 or later. |
22
+
|[08.00.04]|[09.01.01]||
23
+
|[07.04.02]|[08.00.04]||
24
+
|[06.02.08]|[07.04.02]| DNN 7.0.0 has some additional changed pre-requisites, please see the [DNN 7 Developer Quick Start][dnn7qs] for further details. |
25
+
|[05.06.08]|[06.02.08]||
26
+
|[05.04.04]|[05.06.08]||
27
+
|[04.09.05]|[05.04.04]| DotNetNuke 5.2.0 introduced the requirement for SQL 2005 and ASP.NET 3.5 SP1. <br/> 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. <br/> 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][dnn-xml]. |
28
+
|[04.06.02]|[04.09.05]||
29
+
|[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. <br/> With 4.6.2 DotNetNuke introduced functionality known as xmlmerge which automatically does the web.config merging on your behalf. |
30
+
|[04.03.07]|[04.04.01]||
31
+
|[03.02.02]|[04.03.07]| Bumped ASP.NET to 2.0, also see [Upgrade to DotNetNuke 4.x chapter][dnn4x]. <br/> This blog post also contains information about upgrading from 3.2.2. to 4.x: [Preparing for an upgrade][prep-upgrade]|
> 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](https://github.com/dnnsoftware/Dnn.Platform/releases/tag/v9.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.
38
66
39
67
> [!NOTE]
40
68
> 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](xref:setup-upgrades-post-10.2.0)
41
-
42
-
> [!TIP]
43
-
> **Upgrade Notes:** DotNetNuke has been around since 2002, and in that time has had a number of changes which can complicate matters during the process of upgrading through different versions. Please review the list below carefully:
44
-
45
-
## Notes, Requirements, Changes, and Prerequisites
46
-
- DNN 10.2.0 introduced a new simplified upgrade process, see [Post-10.2.0 Upgrade Guide](xref:setup-upgrades-post-10.2.0).
47
-
- DNN 10.2.0 introduced a [new CDF replacement](https://github.com/dnnsoftware/Dnn.Platform/issues/6643) (affects themes/skins) and removed CSS/JS bundling and minification
48
-
- DNN 10.1.1 new installs use SHA256 as the default password hashing algorithm. This only affect new installs, if you want to migrate an upgraded site to SHA256, please read [the documentation for membership provider changes](xref:security-membership-providers).
49
-
- DNN 10.0.0 introduced minimum requirements for ASP.NET 4.8 and SQL Server 2017. In addition, it will force-remove DNN-Provided Telerik versions.
50
-
- DNN 10.0.0 is a significant release with both [Breaking Changes and New Features](https://dnncommunity.org/blogs/Post/20257).
51
-
- DNN 9.8.0 (and above for the 9.x series releases) brings the OPTIONAL (but HIGHLY RECOMMENDED) [Telerik Removal](xref:setup-telerik-removal).
52
-
- DNN 9.4.0 introduced a minimum requirement of ASP.NET 4.7.2.
53
-
- 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 [https://github.com/dnncommunity](https://github.com/dnncommunity). If you have other modules installed, please check for updates before upgrading to DNN 9.2.0 or later.
54
-
- DNN 7.0.0 has some additional changed pre-requisites, please see the [DNN 7 Developer Quick Start](https://www.dnnsoftware.com/wiki/dotnetnuke-70-developer-quick-start#Pre-requisites_0) for further details.
55
-
- DNN 5.3.0 upgrading from a version before 5.3.0 to after 5.3.0, you may encounter this error during the upgrade: “Type 'Web.HttpResponse' is not defined.” This error primarily occurs if an the XML module is already installed. To prevent this, please check PRIOR to upgrading if the XML module is installed in your DotNetNuke version. If it is installed, please upgrade it PRIOR to upgrading DotNetNuke to version 4.3.5, available at [DNN.XML Module on GitHub](https://github.com/DNNCommunity/DNN.XML).
56
-
- DotNetNuke 5.2.0 introduced the requirement for SQL 2005 and ASP.NET 3.5 SP1.
57
-
- DotNetNuke 4.6.2 **prior to 4.6.2** site admins had to manually merge a number of 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.
58
-
- DotNetNuke 3.2.2 to 4.3.7 please refer to the Detailed installation guide "[Upgrade to DotNetNuke 4.x chapter](https://www.dnnsoftware.com/LinkClick.aspx?fileticket=gOZGbvrVKJw%3d&tabid=478&mid=857)". This blog post also contains information about upgrading from 3.2.2. to 4.x: [Preparing for an upgrade](https://www.dnnsoftware.com/community-blog/cid/135317/preparing-for-an-upgrade)
59
-
- DotNetNuke 3.x to 4.x changeover - DNN 3.x used ASP.NET 1.1, whereas DNN 4.x and above require ASP.NET 2.0.
0 commit comments