This is a follow up of
As noted, this is one of the few books around that shows you end-to- end how to build a functioning application, discusses why a choice was made, and has a sample application that just works with almost no messing around. :)
That said, I agree with those who suggest that the sample code be broken up by chapters or modules. As things stand, the finished application though it is separated vertically, is monolithic in terms of its modules, and it's very difficult to identify a "base application" - say the masterpage, the membership section and associated admin pages, and the basepage, bll and dal classes.
Suppose you want the content management part, but not the store. There are many hardcoded references, and now the quickest way to find them is the leave the store pages, bll and dal code out, and then compile to find errors in other support files. Not nice.
As a book to teach intermediate programming, its definitely worth the read, and a careful look through the code, but it would be much more useful if there was a way to extract a runnable base application, that we could add to as we saw fit.