- Use promo code PRIMEBOOKS18 to save $5.00 when you spend $20.00 or more on Books offered by Amazon.com. Enter code PRIMEBOOKS18 at checkout. Here's how (restrictions apply)
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.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
There is a newer edition of this item:
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
Special offers and product promotions
About the Author
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
I agree with the other reviewers for the most part.
* Great coverage of the pattern
* Explains anti-patterns and strategies for refactoring towards a DI pattern
* Focus on architecture and best practices
* Very wordy and repetitive at times; but I feel this is just a nitpick. The book is very well done.
The author lost me several times when describing object inheritance relationships. The book could use a few more illustrations but YMMV. Again, a nitpick.
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.