Dependency Injection: A Practical Introduction
What is Dependency Injection? The answers to the question seem to cause more confusion than help. We'll take a look at what Dependency Injection (DI) is, when we should use it, and what design patterns we can use to help us implement it. Benefits range from extensibility to late binding to testability. We can implement DI with or without a container (such as Unity, Ninject, or StructureMap), but we'll see how a container can do a lot of the work for us.
Jeremy Clark is an application developer, technical speaker, and Microsoft MVP with over 13 years of experience in all aspects of the development lifecycle. After hours, he puts together demos and technical articles for JeremyBytes.com, a website focusing on .NET technologies. Other times he can be found shredding on a plastic guitar (or playing a real guitar fairly badly). He lives in Anaheim, CA with a seedling redwood tree and his cats, Amanda and Toby.