Sebastian Leupold wrote:
please be aware, that .net 4.0 is officially supported by DNN 5.3.0 and above only, some of your issues may be caused by running DNN 4.9.5 on .Net 4.0
Hi,
I know the original thread is from some time back.
We have a similar issue based on an upgrade. Some advice would be more than appreciated. We are currently in the process of migrating a DotNetNuke 4.9.0 application running on .NET 3.5. We have a custom membership provider and a large number of custom modules.
Out first step has been to move the application in to VS2010 and target IIS 7.5 running .NET 4.0. The application runs fine and all the bespoke modules work perfectly.
However, none of the DotNetNuke Admin and Host functions work. One example is the Module Settings page. Clicking on the edit module setting sees the page loop. No errors appear in the DotNetNuke error log. However the web server log lists a large number of “Error 302” lines following each click to the module settings page.
Our target version of DotNetNuke would have been 6.0.1 if the above issues had not arisen. It appears we have a mix of issues between DotNetNuke and .NET compatibility.
What I would be interested to know is what would be a suggest migration path from 4.9.0? From 4.9.0 to 5.3.0 and on to 6.0.1.
Much thanks