1 / 13

An Introduction to IoC Containers with Castle Windsor

An Introduction to IoC Containers with Castle Windsor. Mike Hadlow mikehadlow@yahoo.com mikehadlow.blogspot.com. What am I going to talk about?. The problem: Application Architecture. What is Inversion of Control? Inversion of Control Container. A Real Application: Suteki Shop.

maire
Télécharger la présentation

An Introduction to IoC Containers with Castle Windsor

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. An Introduction to IoC Containers with Castle Windsor Mike Hadlow mikehadlow@yahoo.com mikehadlow.blogspot.com

  2. What am I going to talk about? • The problem: Application Architecture. • What is Inversion of Control? • Inversion of Control Container. • A Real Application: Suteki Shop.

  3. Applications do not scale Complexity Features

  4. Break large pieces into smaller pieces

  5. IoC design style • Systems are composed of small specialised services • Represented by interfaces • Components declare • The services they provide (by implementation) • The services they require (by DI) • Components do not dictate their own lifestyle • Do not implement singleton yourself • Let TDD drive your design

  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 (Hammett) • Also includes: • MonoRailMVC framework for ASP.NET • ActiveRecordbased on NHibernate

  8. How dependencies are resolved Reporter IReportBuilder IReportSender

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

  10. Cons? • Not another thing to learn? • Higher level of abstraction • Performance? • Lifestyle mistakes can be hard to diagnose

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

  12. Resources • Castle Project castleproject.org • Oren Einiayende.com • Krzysztof Koźmickozmic.pl • Alex Henderson bittercoder.com • ALT NET http://tech.groups.yahoo.com/group/altdotnet/

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

More Related