The document discusses inversion of control (IOC) and dependency injection, which are concepts that relinquish managing dependencies and instead allow dependencies to be passed into an object. It recommends using constructor injection to set dependencies and outlines benefits like improved testing, reuse, and simplicity. It provides tips on implementing IOC like minimizing container entry points and avoiding magic strings. Resources for further information on specific IOC tools and a training course are also listed.

1. Practical Inversion Of Control Matt Hinze

2. Agenda What is this talk about The what and why of IOC How to do it Usage scenarios

3. ?

4. EmailSender

5. WorkflowStepper

8. new

9. Relationship is set at compile time.

10. new isn’t always viable.

12. Inversion of Control A concept Relinquishing the responsibility of managing dependencies. Dependency Injection A pattern Constructor injection Property injection

20. There is no new

21. Some Benefits Enumerated Testing Reuse Simplicity Construction velocity Fun

22. Don’t use the tool where you don’t need it, in most tests for example. Think of the tool as a “composer” instead of a “container”; minimize entry points. Prefer constructor injection. Try to avoid “contextual binding”; avoid magic strings; favor convention over configuration.

23. Useful Resources StructureMap documentation Autofac documentation Martin Fowler Jeremy Miller Tool-specific mailing lists

25. For More I teach a course in which we do this stuff for three days. We build features in a real system using agile principles and the tools that enable them. For more information: http://www.headspringsystems.com/training/