Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Channels ▼

Jolt Awards: The Best Books

, October 01, 2013 Five notable books every serious programmer should read.
  • E-mail
  • Print

Productivity Award: Dependency Injection in .NET

By Mark Seeman

Mark Seeman's Dependency Injection in .NET is aimed at the large number of developers who have never used dependency injection (DI) or who aren't comfortable enough to employ it routinely. The first two chapters provide a brilliant and remarkably readable explanation of DI and illustrate through well-chosen examples where and how DI makes sense. In this early going, Seeman avoids using a specific framework, which in other books forces the reader to learn particular semantics in order to simply understand the pattern. His explanation of inversion of control (IoC) is conceptual and clear, illustrating the benefits of loose coupling and simpler coding. He then pushes on into a catalog of patterns that rely on DI. Along the way, Seeman also discusses anti-patterns that undercut the benefits DI can deliver. To remedy the latter and to show how DI is best done, the author also expounds on DI refactoring, which shows how well this model can work and how it improves readability, maintainability, and testability of code.

The code is in C#, which means that it will be readable to developers who know Java, C++, or other languages with a C-based syntax. However, once the basics have been explained and the patterns and anti-patterns explored, the book dives into DI frameworks for .NET, notably StructureMap, Castle Windsor, Ninject, and Unity. It also explains integration of DI with Microsoft ASP.NET.

There are certainly other books on the market that cover DI and IoC, but none of them explain the principles and the design of these patterns as well or as thoroughly as this book. It's the definitive guide to DI and the first place architects and implementers should turn for a truly deep and complete understanding of the pattern — regardless of whether .NET is part of their toolkit.

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.