20080531 Intro To Dependency Injection & Inversion Of Control
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

20080531 Intro To Dependency Injection & Inversion Of Control

on

  • 4,301 views

Presentation from the May 31st 2008 Desert Code Camp

Presentation from the May 31st 2008 Desert Code Camp

Statistics

Views

Total Views
4,301
Views on SlideShare
4,284
Embed Views
17

Actions

Likes
0
Downloads
92
Comments
0

3 Embeds 17

http://www.slideshare.net 14
http://bygandhi.blogspot.com 2
http://bygandhi.blogspot.jp 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

20080531 Intro To Dependency Injection & Inversion Of Control Presentation Transcript

  • 1. Presenter - Donn Felker
  • 2.
    • Senior Consultant for Microsoft Gold Certified Partner- Statêra.
    • 8 years of experience in developing and architecting enterprise solutions.
    • Certifications:
      • Microsoft Certified Technology Specialist
      • Certified SCRUM Master
      • ITIL Foundation Certified
    • Bachelors of Science in Software Engineering
    • Member of FooTheory Community ( www.footheory.com )
    • Blog: http://blog.donnfelker.com
    • Email: [email_address]
  • 3.
    • Present Dependency Injection and Inversion of Control in an understandable fashion
    • Present each topic at a detailed but comprehendible level
    • Give you the resources used in this talk so you can reference them in the future.
  • 4.
    • Confuse you.
    • Pretend to be an authority in patterns, because, well … I’m not.
    • Get all “Fowler” on you.
    • Have theoretical conversations about practicality of the example apps I’m using for demonstration purposes.
  • 5.
    • What is a Dependency?
    • Dependency Injection Pros/Cons
    • Simple Application Architecture
    • Example Application High Level Architecture
    • Demonstration 1
      • Identifying and Breaking dependencies
    • What is Inversion of Control
    • Demonstration 2
      • Custom Dependency Container
      • Introducing Microsoft Unity Container
    • Questions
  • 6.
    • Some common dependencies include:
      • Application Layers
        • Data Access Layer & Databases
        • Business Layer
      • External services & Components
        • Web Services
        • Third Party Components
      • .NET Framework Components
        • File Objects (File.Delete(…), Directory.Exists(…))
        • Web Objects (HttpContext, Session, Request, etc)
  • 7. BROKEN BUILD! CI Server
  • 8.  
  • 9.  
  • 10.
    • Code is tightly coupled
    • Difficult to isolate when testing
    • Difficult to maintain
      • If I change ComponentX how do I know what else it will affect? Did I break anything?
        • If tests are in place they can be your safety net
  • 11.
    • The ability to supply (inject) an external dependency into a software component.
    • Types of Dependency Injection:
      • Constructor (Most popular)
      • Setter
      • Method
  • 12. Injecting a ICustomerRepository and a ICustomerDTOMapper through the constructor. Note: This is the most popular type of injection.
  • 13. Injecting a ICustomerRepository through the setter.
  • 14. Injecting a ICustomerRepository as well as an integer dependency.
  • 15.
    • Pros
      • Loosely Coupled
      • Increases Testability (A LOT!)
      • Separates components cleanly
      • Allows for use of Inversion of Control Container
    • Cons
      • Increases code complexity
      • Some Jr. Developers find it difficult to understand at First
      • Can Complicate Debugging at First
      • Complicates following Code Flow
  • 16.  
  • 17.
    • Lets See Some Code…
  • 18.
    • Sometimes referred to as Dependency Inversion Principle (DIP)
      • The principle states that high level or low level modules should not depend upon each other, instead they should depend upon abstractions.
    • Specific implementations (object instances) are deferred to a higher level of abstraction of control.
      • Examples:
        • Parent class(es)
        • A Container
    • Referred to as the “Hollywood Principle”
      • “ Don’t call us, we will call you.”
  • 19.
    • The best example is to see it in code.
  • 20.  
  • 21.
    • Containers
      • Windsor: http://shrinkster.com/ym6
      • Unity: http://shrinkster.com/ym5
      • Structure Map: http://shrinkster.com/ym7
      • Spring.NET: http://shrinkster.com/ym8  
    • Unity Screencast (PnP Guidance)
      • http://shrinkster.com/yma
    • Good Book to help break dependencies:
      • Working Effectively with Legacy Code (Michael Feathers)
        • http://shrinkster.com/ym9  
    • Contact Me
      • [email_address]
      • http://blog.donnfelker.com
        • All resources from this talk will be posted within 24 hours on this blog.