First time at my blog? Check out the table of contents! x
posted on Saturday, February 28, 2009 11:47 AM |

image

Those of us that have been creating DotNetNuke modules over the years know that there is no one-stop source for information on module programming. You can find particular pieces of knowledge on the internet, but more often than not, the information you are searching for is spread out over dozens of different websites, and is often incomplete.

Until Now

I personally have had to deal with the task of teaching myself module programming using the vast fragmented body of information available on the internet. That’s why today I am excited to tell you about the new book by Mitchel Sellers entitled Professional DotNetNuke Module Programming. This book is the essential guide for any programmer who has the task of developing for DotNetNuke. I am so blown away by this book that I have to say it again: This book is the essential guide for any programmer who has the task of developing for DotNetNuke.

Stop reading this blog post and go order a copy right now!

What Makes This Book So Special?

I’m not going to lie to you. Programming a DotNetNuke module can be a real pain in the ass. If you don’t know how to avoid the millions of gotchas and you are not aware of the best (essential) practices involved, then most of what you write is going to be wrong.

Mitchel Sellers is one of the most experienced DotNetNuke module programmers out there. During his many years involved with DotNetNuke, he has figured out how to create modules correctly and successfully. Mitchel’s prolific amount of experience and knowledge is infused throughout this book. And this is knowledge that you cannot afford to not have if you intend to create successful DotNetNuke modules.

What’s Covered In This Book? Almost Everyting.

This book demonstrates a real-life example of the entire module development process. You will learn how to setup a proper development environment, not only using the Web Site Project (WSP) method, but also using the lesser documented Web Application Project (WAP) method. You will learn the best practices for structuring you module, separating concerns into a data access layer, a business logic layer, and a view. You will learn the proper DotNetNuke integration points. You will learn how to properly debug and package your module for distribution. And that is just a sampling of what is covered in this book.

You can see a complete overview of the book’s contents at the Wrox website.

Summary: You Need This Book

I could continue saying great things about this book, but I’d rather simply urge you to go out and get a copy. This is simply the single most important DotNetNuke book to have in your library. So what are you waiting for? You need this book.

Comments Leave Yours...
Paul Bolejack
4/10/2009 3:30 PM
# re: Book Review: Wrox Professional DotNetNuke Module Programming by Michel Sellers

Rafe,
I was reviewing the book on Amazon & Wrox and recalled your "The Basic Are Just Not Enough..." article, so I thought I'd see if you had anything more to say. And you do. Thanks for sharing your thoughts. But I was a little surprise by your enthusiasm. My impression from looking at the table of contents and sample chapters was that it fell short. If you could answer a few questions about the book, I'd appreciate it.

- Does the book cover issues like you addressed in your data access layer article?

- When the book discusses structuring your module, does it address the benefits of various ways organizing your controls. For example, in the config files, the dnnStore module has 5 folder elements (same name but different friendly names), each with one module element that contains 1 to 3 controls. The dnnBlog module has one folder element, with 5 module elements that each contain 1 or more controls. And the controls are not unique. Some controls are defined in multiple modules. Does the book provide any guidance in choosing one style over the other?

- Same questions at the control level. Does the book help the reader understand when to use multiple asp:panel objects in a single control vs dynamically loaded controls vs multiple controls?

Thanks. I feel like I waste a lot of time looking for resource when I could have been coding/experimenting.

Rafe Kemmis
4/19/2009 10:05 AM
# re: Book Review: Wrox Professional DotNetNuke Module Programming by Michel Sellers

Hi Paul,

The book covers the DAL topic pretty well. Most everything in the book is demonstrated using a real-world example. The module he builds in the book breaks the code up into layers (ie separation of concerns), and so there are classes for Views, BLL, and DAL. He also uses stored procedures at the db level. Besides the examples, he take the time to explain everything that is used in the example, so you don't so much have to read through the code to learn. The examples are mainly there for reference.

Regarding the structuring of your modules, Mitch does a decent job of discussing the different entities a module can consist of. For instance a module can consist of one control that exists in only one content pane, or it can consist of multiple controls that can be distributed between different panes on the same DNN page.

He also discusses how you can structure the "Views" of your page and navigate between them. I think he offers 3 or 4 different suggestions on how you can choose to work with views. All in all I think he sums up the options pretty well.

Post Your Comment

Title
Required
Name
Required
Email
Optional
Url
Optional
Comment  
Please add 8 and 2 and type the answer here:

Who Is Rafe

rafe

Rafe Kemmis

I am an audacious web developer with a double bachelor of science in Computer Science and Mathematics. I specialize in Microsoft ASP.Net, Silverlight, and Adobe ActionScript.

Questions?

Always a thoughtful response. You may post your question on an article, or contact me directly.

Hire Me.

I provide custom solutions to complex problems. I can help your business no matter how large or small.

Contact me now.

Subscribe