After you have changed the .NET Runtime Version you must restart the Application pool!  Also clear your browser cache please.

---

Regards

Matthias

DNN MVP

www.aarsys.de

Metro7 Skin

ShoutCastStats Module for DNN

I want now give you a personal statement of me to 3rd party modules as you mentoring in your post. DotNetNuke looks to make not much braking changings, and always looks that modules also running on a newer version. But the technologie always is going forward and sometime a braking changing must done. If DotNetNuke doing a breaking changing they doing it public and all vendors could use the betas to check thier own modules and bring out a newer version if they have then any issues due a breaking changes. Personally I worked since 2005 now with DNN and I saw it is the best and secured .NET CMS Framework on the marked. Due to the 3rd party modules I also learned that there are some ventors they more doing releases a product as a hobby, but there also much tey are very professional. Also some vendors are comming and going. So to make sure you always want to have the change that a bued module want run in the future, also if the vendor no longer exists you should buy a source package. If you buy a source package you could get a developer service or doing by self (if you can) a modification on the module. Basicly I don't think that it is the work of the DotNetNuke Corperation to make sure that an application of a 3rd party vendor is formed well, always updated and give the support for this. This is the part a vendor have to done. About the use of DotNetNuke I know some insides knowledge to Adminstration of Networks and SQL are needed. But I am sure all this is needed to the most CMS too. Why some usersers moved to use a other CMS I can't know. But what Iam know is that some other solutions are more user friendly to use it, but they are then more restrict on extend it. DotNetNuke if self is not only a CMS, it is a Framework that is very flexible to build applications. This flexibilly is what the most users like, without restriction of security and to the UI. DotNetNuke also doing a lot to give the users a start base on using DNN, they allready all bloged from Joe Brinkman (please check his blog on this site). To bekome more internals on managing a DNN I also can suggest a Book - DotNetNuke 5 User's Guide - from Wrox. One other thing I see on the last months is that we got many users that previously used any Linux or php based CMS before. They all are having more knowledge how to use a Solution on a php based system, and they wondering why things not going the same way as he have learned before. But it is a nature that all systems going a other way and we have to learn it. Now back to your issue: I have also try to use .NET 4.0 and going back to use .NET 3.5 and have to remove the runtumeVersion on my web.config file. Then I restarted the website and the application pool, and all going well. It could be you have to try to open your website from a 2nd system if you can't login, due some browser issue. It could be very difficult what happens on a instance with an issue. So sometimes it needed a higly internal know of the System where DNN is running. We who try to help the community are restricted with informations we get from them. Also it is not possible to think on all issues anyone had made before, and we didn't get that info. I've sometimes had made a offer for a personaly assistance, and I am sure there a lot DNN professionals that want do this also if you ask them. Resume, I don't think it is a issue from DotNetNuke. I think more the issues are related to any 3rd party modules or on your settings of DotNetNuke.

---

Regards

Matthias

DNN MVP

www.aarsys.de

Metro7 Skin

ShoutCastStats Module for DNN

There are not basic major changes on DNN 5.5.1.  The basic opinion for this release was the workaround to make it a litle harder to exploid the .NET vulnerary.  But I know that on some shared hosting some users with you shared the hosting doing also a hard use of the server resources.  So also some other users could doing some of the performence issues you have.  Then it could also be that some of the 3rd party modules you are using having any problems with some workaround. 

I have running some customer sites on shared hosting, without any issues. Also I have a own Web Server with only 1 GB that running more then one instance of DNN and also running the SQL server, as E-Mail Server and as Broadcasting server (Audio Streams) and have no issues.  Sure it could always be faster but this needs then a better hardware and more memory.  I am very happy with the performence since DNN 5.5.  All instances on that Server running DNN 5.5.1 without one professional licenze, that I still have to upgrade soon.

---

Regards

Matthias

DNN MVP

www.aarsys.de

Metro7 Skin

ShoutCastStats Module for DNN