The Basics Are Just Not Enough When Implementing A DotNetNuke Module

You've been kicked (a good thing) - Trackback from DotNetKicks.com

I agree that more advanced information is needed, however, my site does cover advance topics such as Module navigation options, Data Access options, Web services and Silverlight.

Thanks for the feedback Michael. Let me compliment you on your site. The tutorials there are very helpful and have been an important contribution to the DNN community!

However, I still wish there was more information out there on the specifics of the framework. What good is a framework if developers don't know how to use it? The existing documentation is what sets DNN apart from other less documented system, such as Community Server. It is important that we empower developers as much as we can so that DNN keeps improving and being used.

I have to agree with Rafe!

What we need is more full documentation on creating Modules. Like an API type Listing so that we can find what we need very quick.

A user should not have to spend weeks asking in forums and searching the web to try to find out how to impliment something into a Module.

Ray

I have to agree with Rafe here. The documentation for DNN is simply not up to par and needs a complete overhaul.

While I do think Mike has done a good job filling the void (as well as Mitchel Sellers, DnnCreative and others), there is a serious lack of advanced module development documentation for anything other than creating a simple Hello World module for Dnn.

:-)

The Professional Modules book is intended to cover the entire module development process, from downloading DotNetNuke and setting up a new module project and Visual Studio all the way to refactoring and releasing module upgrade versions. The book not only lists the API and control options available to module developers but also provides real world examples of how and when to implement them.

As a contributor to the Pro 4 book, I also understand what that book had covered and avoided covering the same topics for a second time. To summarize the book up better than any description can, I basically set out to write an entire book I would hand off to new developers at my organization to teach them best DotNetNuke practices.