difference between factory pattern and Dependency Injection

Also, if you look into any of the DI tools, they supports attributes. If I specify that in a class, the constructor is used to create a dependency object by decorating the constructor with an attribute the DI tool will generate the dependent object for you while creating an object for the class and you do not need to specifically tell the tool or you create dependent objects in your code. Similarly you can decorate any property that is creating a dependent object or a method by the attributes supported by DI containers like Ninject, Unity or StructureMap, they will take care of creating objects for you.

So, in a way as said in the previous comment DI is highly evolved form of Factory pattern.

In simple terms, Dependency Injection is a design principle or architectural pattern for loosely coupling software components. Factory pattern is separating responsibility of creation of objects of classes to another class.

In a way, DI is an evolution of Factory Pattern.

The following post may make things clear:

http://codefornothing.wordpress.com/2007/11/11/why-use-dependency-injection/