ASP.NET MVC 1.0 Test Driven Development by Emad Ibrahim

Claim your money back!

Rating 2 out of 10

Don't buy this book! This book is full of errors in the extreme! The first chapter dealing with code is chapter 3 starting on page 35. Already on page 56 I gave up reading the book, because I don't wanna spend my time debugging Emad Ibrahims code. In the span from page 35 to page I detected technical errors in the code on page 39, 41, 43, 44, 45, 49, 50, 51! I have submitted these errors to the errata page for the book on Wrox.com. So I managed to read 24 pages of the part of the book descibing the code and as said I detected serious technical errors on 8 out of those 24 pages! That gives an error procentage of 33% for the pages describing the code! That's very very Harsh! I don't know too much about the legal issues, but I would guess that we as customers are entitled to have our money returned from this title, there are simply far to many errors in the code to that it is acceptable! I mean it's not that Emad Ibrahim is unknowledgeable, on the contrarary, he is very knowledgeable, but he is just like a happy beaver coding away, not caring about the mess he has left behind. It throws a very dubious light on Emad Ibrahim as a conscientious writer. But especially it throws an enormous dubious light on Wrox.com as a publishing company! How could they release this book? Don't they practice any kind of review on their books? Apart from the errors I have mentioned in the technical code part of the book I also detected an error in chapter 2 on page 34. Ibrahim lists the tools we need to follow along in the book. He recommends that we shall use ReSharper to run our MbUnit tests, but he forgets to tell that you also need gallio.org to run MbUnit test with ReSharper. Also the source code for this book is badly organized. During the book Emad Ibrahim is constantly refactoring his code, I think it would have been appropriate if there had been a source code for each chapter so that you could easily figure out the present state of the code. Instead the source code has been left as one big chunk, then you have to yourself try to figure out what the code at the present state in the book might look like. Well after all this negativity, proberly the book is ok without all the errors. If you are very skilled you will maybe easily solved the errors and be able to have a good reading experience. But for a less skilled person this book seems to be a real trap!