Top critical review
11 people found this helpful
Too much too soon
on 4 February 2011
This book gets too complicated too soon. It started OK, with some theory that appeared to make sense, but in the example project the author tells you to create all sorts of weird and wonderful folders in additional to the standard ones.
After following along for quite some time, I realised I hadn't got a clue what most of the stuff I'd created was for, whether it was an M, a V or a C, or where to look for a particular file! First he divides the top level into Domain and WebUI; then he adds Abstract and Concrete subfolders to Domain and HtmlHelpers and Infastructure to WebUI. Then he tells you to install third party extensions for Dependency Injection.
For someone trying to understand the MVC concept this was just too much. A free download of the first chapter of the other book, Professional ASP.NET MVC 2, proved much more helpful. Having ditched my first project and started again using this example my project now has folders called Models, Views and Controllers - no ambiguity there - plus a couple of other folders whose function is pretty easy to understand.
I suspect the author of this book has developed his folder structure as a result of his experience on projects; it probably works for him, but for a beginner struggling to understand new concepts it is not appropriate.
For reference my background is in web development and programming but not, until recently, ASP.NET or C#.