I've been doing DotNetNuke module development for several years now, but still find the experience messy, bitty, fragmented and generally dissatisfactory.

Coming from a professional software development background I don't feel comfortable unless a given project is in a state such that I can come back to it 6 months later and carry straight on working.

Every module development setup I've used for DNN has been different, and it seems to me that with each new DNN release, the previous setups break.

So I brought the Mitchel Sellers book in the hope of finding a satisfactory, repeatable process for creating and working with visual studio and a DNN module project.

Generally the book has exactly the style I was looking for. Detailed explanation with some high-level context without being patronising to a professional developer.

The first thing that annoyed me about the book was that I couldn't get it on safari books online. It's damned difficult to juggle the book and my notebook on the train, but I won't hold that against the authors :)

I'm enjoying the process of working through the book, but I have hit a few snags - I'm going to blog in further the issues and work-arounds here so that I have a record of the total process (and on the off chance it's useful information to others).