DotNetNuke 4.x

I use DotNetNuke extensively for building Enterprise applications for my clients (you might be interested in checking out iClinic, or iMLM etc.). DNN together with ASP.NET & Sql Server put forward extreme power and flexibility in your hands as a Solution Architect, together with great off-the-shelf features, a perfect platform to build upon.

You might be well aware that DNN allows you to create multiple Portals based on the same physical installation and the database. It even allows the users to be managed independently across Portals, restricting users to the Portal they registered for.

I thought about writing this blog entry while doing a technical review of a book on DotNetNuke 5.x. The soon-to-be-published book (by Packt Publishing) says this about DotNetNuke portals:

I present below various Tips & Techniques (not in any particular order) for optimization of a typical DotNetNuke installation.I learned these while using DNN over time, while I encountered some of them while browsing over web.

A typical DNN install requires considerable server resources, and creates significant traffic between the database & web server. These techniques aim to reduce both of these where-ever possible, along with some other optimizations. Some of these may not apply to you, and I advise you to exert discretion in deciding which of these work best for you.