Taking a look at DotNetNuke 4.5

While I'm a SharePoint guy thru-and-thru, I still like DotNetNuke think Shawn Walker and the community have done a bang-up job getting it to where it is today. It's now reached version 4.5 and includes some new features like support for Microsoft AJAX. I still struggle with module development for DNN and find writing SharePoint Web Parts (especially 2007) much easier, but PAs rule the planet for extending functionality where you don't have server access like you need for SharePoint.

Here's a quick rundown on things I've noticed in the new version of DotNetNuke.

The immediate thing you'll see is the improved header when logging in as admin or host.

It's a lot cleaner and takes up a lot less real estate. Don't worry, the old header is there via an AJAX collapsible panel so it's just a click away:

All the regular tasks are there, including a new Design view. This allows you to see the page but without the content in each module. The View vs. Edit mode is just like the old Preview mode so that's still there.

What's new is the Solutions Explorer. This is a DotNetNuke marketplace type module that comes built-in via the Host menu:

Looks very interesting and it loads the content each time you view it, so it's a portal to the live site to always keep you up to date.

If you're like me I use the default accounts (host/dnnhost and admin/dnnadmin) however if you still leave those passwords intact for those accounts you'll see something like this when you login:

It's a nice little feature to let you know your Host or Admin account could be compromised. I actually stumbled over a few DNN sites out there and for kicks would log in as admin, then send the admin and email telling him to change the password.

Other small but nice changes I've noticed are like the host settings screen displays relative and physical paths where DNN is installed (sometimes nice to know on a hosting environment).

Overall it's a great release, supports AJAX (Atlas, or whatever it is we're calling it these days) and looks like another solid version to build your community sites on.

6 Comments

  • Let us not forget the new and improved web installer that allows you to choose everything you want right from the word GO!

  • Simple and nice review.
    Some advise, do not use Wizard Installer at Medium Trust environments, especially Godaddy root installation. Because they wont pass permission test.

  • Actually we have found that developing Sharepoint Web Parts is much more time consuming than DNN Modules. For implementations you have to modify the web config of Sharepoint to even add a new web part? Besides that you don't get the ability to use user controls directly, all of the back end administration has to be done by building the edit controls dynamically? Maybe I am missing something?

  • Actually we have found that developing Sharepoint Web Parts is much more time consuming than DNN Modules. For implementations you have to modify the web config of Sharepoint to even add a new web part? Besides that you don't get the ability to use user controls directly, all of the back end administration has to be done by building the edit controls dynamically? Maybe I am missing something?

  • mrjamesbound,

    Did you think maybe that it was your doing and not the framework's problem? If 400 000 users don't seem to be having much problems, and you do, and if most skinners in the world are VERY happy with the skinning and css model, and you are not.

    I cannot understand how you can be so arogant to say such things without first looking at yourself.

    As about the learning curve... imagine, you have to be a seasoned developer to be able to develop it... well here is a reality check... these features are not for novice developers. They are made for advanced users to give them more power - and I as such a user don't have any problems doing these things.

    My 2 cents....

  • Chad Nash,

    I've them both, and done consulting and education on developing both web parts and modules so I have quite a lot of experience with them (Sharepoint and DNN).

    The only thing I can say after doing things like these both for my company projects and educating other people how to use it... After developing with DNN, developing for Sharepoint is a PAIN.

Comments have been disabled for this content.