Yes, there is some scope for improvement here. But it is ridiculous to criticize the author for not making the book longer. My shelves are groaning under the weight of huge computer books, bloated with information that is readily available elsewhere.

Instead of padding out his book, Mitchel tells you where to get the information you need.

What Mitchel does supply, that I haven't seen anywhere else (except his site), is a full treatment of the Web Application Projects (WAP) route to module development. WAP vs WSP is one of those stupid religious wars.

What Mitchel doesn't say (but probably should) is that the alternative Web Site Projects (WSP)route may not get you where you want to go. He merely observes that "there are ways to create compiled assemblies from WSP projects but they are very complex to complete". But, if you have a complex module or suite of modules, you may simply be unable to compile them as a WSP. I have learnt that the hard way.

His book is not just the best treatment of WAP development in DotNetNuke, but the only one. For that alone it is worth the bucks.