1 / 15

The Castle Windsor Inversion of Control Container

The Castle Windsor Inversion of Control Container. Mike Hadlow mikehadlow@yahoo.com mikehadlow.blogspot.com. What’s wrong with this code?. IoC Reporter. We can now test Reporter. IoC == Component Oriented Dev. Wikipedia says: Multiple use Non context specific

logan-franklin
Download Presentation

The Castle Windsor Inversion of Control Container

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Castle Windsor Inversion of Control Container Mike Hadlow mikehadlow@yahoo.com mikehadlow.blogspot.com

  2. What’s wrong with this code?

  3. IoC Reporter

  4. We can now test Reporter

  5. IoC == Component Oriented Dev Wikipedia says: • Multiple use • Non context specific • Composable with other components • Encapsulated • A unit of independent deployment and versioning

  6. What is an IoC container? • A (very) smart factory • Automatically resolves dependencies • Automatically injects concrete instances • All services are registered in the container • Single point of access for services • Transparent • Various implementations for .NET

  7. Castle MicroKernel / Windsor • Part of the Castle Project castleproject.org • Started by Hamilton Verissimo • Also includes: • MonoRailMVC framework for ASP.NET • ActiveRecordbased on NHibernate

  8. Reporter with Windsor

  9. How dependencies are resolved Reporter IReportBuilder IReportSender

  10. Pros? • Simpler component architecture • Reduced cost of change • Easy to unit test • Easily move between application configurations • Ready made configuration (IoC containers)

  11. Cons? • Not another thing to learn? • Higher level of abstraction • Can’t do obfuscation and configuration

  12. Should I use it? • Already familiar with OO principles and patterns? • Already writing unit tests? If not, learn how to do these first Don’t impose an IoC container on a team which can’t see its benefit

  13. A Real Application http://code.google.com/p/sutekishop/ http://sutekishop.co.uk/

  14. Resources • Castle Project castleproject.org • Oren Einiayende.com/blog • Alex Henderson bittercoder.com

  15. Questions? Mike Hadlow mikehadlow@yahoo.com mikehadlow.blogspot.com

More Related