How to upgrade DotNetNuke from 3.1 to 4.0?
Top : DotNetNuke
| Article ID: |
 |
000062 |
| Rating: |
|
0.0 / 5.0 (0 votes)
|
| Views: |
|
3671 |
|
|
How to upgrade DotNetNuke from 3.1 to 4.0?
|
If you would like to upgrade to 4.0 from 3.1, the procedure is not that much different from any other upgrade. The only real issues relate to the radically different structure of the web.config file (due to .NET2 changes). The recommended procedure is as follows:
- backup web.config (rename to web_old.config or other similar name)
- rename release.config to web.config
- move any user customised items from the backed-up (old) web.config to the new web.config. these can include
- machine keys - move these from old node to new node. Note that in .NET 2 rather than two separate elements under AppSettings the machineKey is now one element with two attributes.
- connection strings - move this to both the element (for support of legacy modules) AND the new element (for support of DNN4 core and Asp.Net Membership)
- objectQualifier - this goes in the usual place
- customised provider sections need to be updated to reflect your old settings
- Enable your site to support ASP.NET 2.0 in Helm http://www.databasemart.com/Support.php?x=&mod_id=2&root=8&id=55
- Browse to your site
|
