After working on DNN for more than 2 weeks, I have concluded that DNN cannot be used for a "Business Critical" project.  I understand people can have learning curve issues (like me), but looking at DNN from a business point of view in three critical areas (Repeatable installation, support for current installation, upgrade installation)  DNN meets none of them with respect to the attributes of a "Business Critical" implementation.  Specific points:

DNN "installation" is not reliable:

1.  If you install one version of DNN vs another (say portal vs install), you cannot reliably have the same final installed product.

2.  Each time you "install" the same version you cannot reliably expect the same final installed products.

DNN "support" in not predictable in either "problem report to response" or "response applicable to issue" or "quality of response":

1.  You post an issue or problem, and then wait.  Maybe an hour, a day, or..... for a response.

2.  You get a response that essentially says "keep looking".

3.  Answers are based on a "try this".

DNN cannot be reliably upgraded.

1.  You download an upgrade which intregrates/applies only with significant manual intervention.

2.  There is no formal maintenance process.

I have to conclude that DNN's primary purpose is as an "academic exercise".   As justification for this view I submit/point to the DNN and ASPNET forums and their posts.

I will pursue DNN, but only as a learning exercise.  I simply cannot recommend it to any of my clients who might depend on it for keeping their business operating.

I'm working witn DNN now for a year and a half (since version 2.1.2), and i found that some factors are critical in putting DNN to good use without problems:

* Because DNN leans on SQL server quite heavily, it helps me that i knew a lot of SQL Server already prior to engaging with DNN. I see a lot of questions of "newbies" that on some level have to do with a wrong sql server setup, db backup, user permissions etc etc.

* I praise myself lucky that i have been a system administrator responsible for webhosting at some of my clients. Having knowledge on how IIS works helps a great deal in setting up DNN. Especially the multi portal feature of DNN has to cooperate with the host header functionality of IIS.

* In my opinion support for DNN is better than any "commercial" product i've ever seen. Name me one commercial product where you get proper feedback when you ask a question. (IMO most help desks of most products start with "it's probably something you are doing wrong")

* DNN is FREE! Which means that there is no callcenter guy waiting for your support question to pop in. Sure we'd all like that, but would you also like to pay thousands of dollars for the product in return?

* The forums over at asp.net, and the forums here at dotnetnuke.com are a wealth of information. It takes a lot of time to keep track of it all, but if you take the time, you can learn a lot!

cheers,

erik

DNN Blog | Twitter: @erikvb | LinkedIn:

I don't have the data to answer the following questions, but the answers would (I suspect) bolster my contention:

1.  How long did it take one to arrive at your first functional installation (functional defined as being able to log on to the install from another system, browse the install and be able to update the install (add users/announcements/etc)?

2.  How many times did you have to "wipe" either the DNN code or the SQL database to get to a functional installation?

3.  Divide the time spent on the forums by the time spent actually installing DNN.  Any result greater than 2.0 adds to my arguement.

4.  Do you wait to move to the next DNN release only when forced by circumstance?

And probably the most telling arguement for my conclusion is based on how you could/can answer these three business questions:

Given you have perused the forums and your superior asks:

1.  How many man-hours and elapsed time does it take to get a functional install?

2.  If something is not working as described, How many man-hours and elapsed time are required to make it work?

3.  Are you willing to base 25% of your annual performance review on meeting/achieving the above?