I can understand that you don't delve into the creating of the SQL objects but there is no indication as to where and what name to give the Database Providers referenced in chapter 13 page 364 if one was creating them from the DotNetNuke Module Template within VS 2005. I'm really frustrated with this book and the complete lack of logical flow. I had great expectations that the authors would talk us through creating a module from start to finish in Chapter 12 with the Hello World module (which I registered with DNN and added to the content pane but found it to be invisible but that's another story) only to find in chapter 13 that we are back to working with the convoluted Solutions folder from the 3.2 build. Why didn't you create a database table and stored procedures for the Hello World module and continue to build on it instead of going back to the Events module in the Solutions folder? I still don't have a clear understanding of how to create a module start to finish. Is there any documentation that walks a "green-horn" through creating a module without having to download and deal with the 3.2 solutions folder and its cumbersome VS project files? Any direction would be appreciated.

I've purchased and recommended the Beginning Active Server Pages 3.0 as well as the Asp.Net 2.0 books. The authors of these books are amazing in their understanding of the subject and logically flowing through the Chapters.

If you bought this book for the purpose of learning how to develope custom modules - as did I. My advice is to close it now and spend your time at http://www.dotnetnuke.com/Community/...s/Default.aspx

This book was not written to be a start to finish for developing modules. The books is an introduction to the API, features, and how to do things. I am currently working on a book for Wrox that is a module development guide start to finish which covers additional topics beyond API such as:
DotNetNuke w/ Source Control
DotNetNuke w/ Continuous Integration (TDD)
DotNetNuke Packaging Automation