DotNetNuke 5 development, and the need for black magic

26. January 2010 22:02

I first started to work with DotNetNuke at the end of its 4th edition era. We had tried a couple of other systems after putting our in-house developed platform to rest at last. That was a really great system, which we (of course) were very fond of, but maintenence and development of new functionality simply was not cost effective enough. What finally landed us on DotNetNuke was its pretty large developer community and the number of modules available.
When the 5th version was released it brought a couple of welcome changes. Unfortunately the documentation part of the new version kind of slipped behind. There is pretty much docs describing the workings of the 4th version and older, but for the 5th there is really not much. In the forums you find people that really know what they're talking about, but it gets kind of scattered when you want to read up on something.

Tutorials for older versions of DNN are plentiful, but for some reason there doesn't seem to be very much for the 5th there either. I admit that the differences in how you do a lot of things in version 4 and 5 aren't very big. But if you're in need of a tutorial you are probably not very familiar with what you are doing, so even small differences can easily put you off track.

This documentation shortage makes it kind of slow to get started. To get to know the system you're left to the dark arts of code crawling, which, as we know, is only for us true code freaks...
I thought I might write up some tutorials in coming posts to see if there is anyone interested in reading them. Think I'll start off with modules, but who knows, I might change my mind...

About the addict

Johan Seppäläinen lives in Uppsala, Sweden. He spends most of his days working as a systems architect/developer, specialized in solutions built on Microsoft platforms.
Occasionally there is time for some recreational coding, when he pursues optimal solutions and code zen, mainly in C#. When he is not writing in this blog, that is.