Woah, Nellie.NET!

From my simple mind to… mine…

Dot Net Nuke and Domain Driven Design

with 3 comments

I’ve always liked Dot Net Nuke. In one of my previous businesses, Enlightened Products, we converted our entire replicated web site infrastructure to DNN and it worked out incredibly well. Given the nature of Network Marketing, it was great to be able to customize skins quickly and integrate our base functionality through DNN’s module infrastructure.

However… the module infrastructure at the time was very immature. Basically, you are required to code the module into the DNN infrastructure, which is fine. The problem is that DNN also teaches direct communication to the database in their training videos and books. There is no “clean” sense of the problem domain in the context of personalization, functional modules, and DNN skins.

Recently, some folks at work have discovered DNN. Great timing… I had been thinking of composing a series on xDD with DNN. So with this extra level of motivation, let’s get this ball rolling.


Written by Nelson

July 22, 2007 at 4:07 am

3 Responses

Subscribe to comments with RSS.

  1. Roll with it! Just curious what is going to be your problem domain?

    Joe Ocampo

    July 22, 2007 at 3:33 pm

  2. As a software integrator for contact centers, I’m interested in your thoughts as an experienced DNN implementer. Also, I notice that you’re publishing here via WordPress and not DNN – I’m considering the feasibility of mixing the two. However, I’m continually surprised by the tightly-coupled nature of open source software’s database access, which makes it nearly impossible to standardize on Oracle.

    Interested Bystander

    August 1, 2007 at 10:59 am

  3. On WordPress, I am using the hosted version. I like maintaining my blog(s) elsewhere. I would find it very difficult to integrate WordPress into DNN, unless it has an domain level API of some sort – at which point DNN becomes the security/presentation portion of the application and you’re set. I’ll have to look into this, because it sounds like an interesting idea.

    In response to your comment on the “tightly-coupled nature of open source software’s database access,” my only rebuttal is that “it depends.” Some applications have this as a requirement, sure. But if any application uses something like NHibernate or, more directly, – as in the case of DNN – the abstracted .NET data provider model, you should not have any problem moving from database to database. That is, of course, as long as you remain stored procedure free!


    August 2, 2007 at 7:33 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: