Email
Favorite
Favorited ×
Download
Embed
Private Content
Copy and paste this code into your blog or website Copy Customize Close
We have emailed the verification/download link to "".
Login to your email and click the link to download the file directly.

To request the link at a different email address, update it here. Close
Validation messages. Success message. Fail message.

Check your bulk/spam folders if you can't find our mail.

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

+ Follow

Inversion of control

by Hasan Jaffal on Apr 16, 2010

1,515 views

Inversion of control design pattern and its implementation, dependency injection and service locator.

More…

Inversion of control design pattern and its implementation, dependency injection and service locator.

Less

3 Embeds 134

http://www.jaftalks.com	121
http://www.slideshare.net	8
http://jaftalks.com	5

Statistics

Favorites: 2
Downloads: 46
Comments: 0
Embed Views: 134
Views on SlideShare: 1,381
Total Views: 1,515

Constructor:In this methodology we pass the object reference in the constructor itself.
IoC pattern is used to enable extensibility in a class or framework.You want to decouple your classes from their dependencies so that the dependencies can be replaced or updated with minimal or no changes to your classes' source code.You want to test your classes in isolation, without using the dependencies.You want to decouple your classes from being responsible for locating and managing the lifetime of dependencies.(IoC) is an old principle in object oriented programming, but it’s gotten a lot of buzz the last couple of years because of the proliferation of Dependency Injection (DI) tools and articles.
A form of the IoC pattern, Dependency Injection (DI), Any of the following conditions justifies using the solution described in this pattern:You want to decouple your classes from their dependencies so that these dependencies can be replaced or updated with minimal or no changes to your classes' source code.You want to be able to write classes that depend on classes whose concrete implementation is not known at compile time.You want to be able to test your classes in isolation, without using the dependencies.You want to decouple your classes from being responsible for locating and managing the lifetime of dependencies.Do not instantiate the dependencies explicitly in your class. Instead, declaratively express dependencies in your class definition. Use a Builder object to obtain valid instances of your object's dependencies and pass them to your object during the object's creation and/or initialization. This better supports testability and growth of a system over time. you are free to choose whichever DI container you want, but you must provide an adapter for it to the IContainerFacade interface.
Constructor:In this methodology we pass the object reference in the constructor itself.Interface: In this methodology we implement an interface from the IOC framework. IOC framework will use the interface method to inject the object in the main class.Public Class Person : IAddressDI{//setaddress comes from IaddressDISetAddress(Iaddress a ){}}Service locator Next slide
Constructor:In this methodology we pass the object reference in the constructor itself.
Setter and Getter: The dependent objects are exposed through set/get methods of classes.The bad point is because the objects are publicly exposed it breaks the encapsulation rule of object oriented programming.
Interface: In this methodology we implement an interface from the IOC framework. IOC framework will use the interface method to inject the object in the main class.Public Class Person : IAddressDI{//setaddress comes from IaddressDISetAddress(Iaddress a ){}}
The other way to inject dependency is by using service locator. Your main class which will aggregate the child object will use the service locator to obtain instance of the address object. The service locator class does not create instances of the address object, it provides a methodology to register and find the services which will help in creating objects.
Constructor:In this methodology we pass the object reference in the constructor itself.
Applications based on the Composite Application Library are composites that potentially consist of many loosely coupled modules. They need to interact with the shell to contribute content and receive notifications based on user actions. Because they are loosely coupled, they need a way to interact and communicate with one another to deliver the required business functionality. To tie together these various modules, applications based on the Composite Application Library rely on a dependency injection container. Dependency injection containers can reduce the dependency coupling between objects by providing the facility to instantiate instances of classes and manage their lifetime based on the configuration of the container. The modules communicate using events but they will access other modules. How? Using containers who inject the dependecies
A container is an abstraction responsible for object management, instantiation and configuration. So you can configure the objects using the container rather than writing client code like factory patterns to implement object management. There are many containers available which can help us manage dependency injection with ease. So rather than writing huge factory codes container identifies the object dependencies and creates and injects them in appropriate objects.

2 Favorites

Jose Marcos da Silva , SharePoint Developer at F|Camara Formação e Consultoria 11 months ago
sprming 1 year ago

Inversion of control — Presentation Transcript

Introduction to the
Inversion of Control
Agenda
- What is a Dependency?
- Example Application High Level Architecture
- Inversion of Control
- Dependency Injection
- Service Locator
- Dependency Injection Pros/Cons
- Unity Container
- Questions
What is a Dependency?
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)
Dependencies at a Very High Level
BROKEN BUILD!
CI
Server
The problem
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
What problems do dependencies create?
Inversion Of Control
Don’t call me, I’ll call you
Dependency Injection is an implementation of IoC
The ability to supply (inject) an external dependency into a software component.
Types of Dependency Injection:
Constructor (Most popular)
Setter
Method
What is Dependency Injection?
What is Dependency Injection?
Dependency Injection
- In DI we have three ways of implementing the same:
- Constructor way
- Setter way
- Method way
Constructor Injection
Setter Way
Method Way
Demonstration
Lets See Some Code…
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
Dependency Injection Pros & Cons
Service Locator
- Form of the Inversion of Control pattern
- It allows classes to locate specific services they are interested in without needing to know who implements the service.
Service Locator
Who will manage the Dependency Injection?
Containers !
Container
A container is an abstraction responsible for object management, instantiation and configuration.
you can configure the objects using the container rather than writing client code like factory patterns to implement object management.
Container
Thanks For Listening.
Practical
“You should be pragmatic with any pattern,
it's not necessary to be applicable for every situation”
Jaffal Hasan
- Mail: hasanjaffal@hotmail.com
- Blog: http://www.jaftalks.com/
- Twitter: http://twitter.com/jaftalks

Inversion of control

by Hasan Jaffal on Apr 16, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

3 Embeds 134

Statistics

Inversion of control — Presentation Transcript