- Paperback: 584 pages
- Publisher: Manning Publications; 1 edition (September 28, 2011)
- Language: English
- ISBN-10: 1935182501
- ISBN-13: 978-1935182504
- Product Dimensions: 7.4 x 1.3 x 9.2 inches
- Shipping Weight: 2.3 pounds (View shipping rates and policies)
- Average Customer Review: 76 customer reviews
- Amazon Best Sellers Rank: #145,138 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Dependency Injection in .NET 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
See the Best Books of 2017
Looking for something great to read? Browse our editors' picks for the best books of the year in fiction, nonfiction, mysteries, children's books, and much more.
Frequently bought together
Customers who bought this item also bought
About the Author
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
I would agree with a review I've read (somewhere...can't remember if it was on Amazon or not...) that there are some prerequisites to reading this book, such as a good grasp of MVC.Net. I definitely got a lot out of the examples, but couldn't help but feel sorry for readers who don't have that background. I'm still giving it 5 stars though. My word of caution to readers before purchasing this book would be to go through some MVC.Net tutorials and at least get familiar with the paradigm itself, the Global.asax file, Entity Framework basics, Controller Factories, and interfaces/abstract classes. You'll get more out of it if you have a basic understanding of these concepts. If you don't, some of the content won't seem relevant.
Lastly, I'd recommend reading the author's blog and Stack Overflow articles. He is one sharp dude. LEARN FROM HIM!
While the author claims that testing is only one of many benefits to DI I don't believe the book bears that out. As a seasoned developer I can't help but ask, if 40% (my estimate) of the code written by developers is to verify that their app works correctly (unit tests) shouldn't one seriously question the appropriateness of the software architecture chosen? I'd much rather see that time go into making abstract software development constructs much more concrete so that future maintainers of the code base can follow what's going on. The hardest part of software development is taking mountains of abstract ideas and creating concrete manifestations of them. Dependency injection does nothing to tackle that problem. In fact is coaches that the developer should code everything to interfaces and keep connections between classes as abstract as possible. At the very least I'm skeptical that such an approach decreases the lifetime cost of the software or decreases the time necessary to adapt the code to new uses.
My hope is that the dependency injection fad doesn't last much longer than the XML/SOAP fad.