The factory method pattern is a creational design pattern used in software development to encapsulate the process of creating the objects. Concerns:

First of all, the definition: “Define an interface for creating an object, but let the subclasses decide which class to instantiate. The Factory method lets a class defer instantiation to subclasses.“ Illustrated by adding a building to our game, which creates various GameUnits for each faction.

The factory method pattern is a design pattern that allows for the creation of objects without specifying the type of object that is to be created in code. A factory class contains a method that allows determination of the created type at run-time.

As application size and complexity increase it becomes more and more difficult to reuse existing components and integrating these components to form an interconnected architecture because of the dependencies of the components. One way to reduce dependencies is by using Dependency Injection, which al...

The article describes how to employ a factory approach to add extensibility to framework code.

The article describes how a factory can be used to achive layer separation within a classical 3-tier architecture and what other bennefits result from such an approach.

The article describes a simple factory implementation and looks into further enhancements.

Dependency injection is gaining momentum, but sometimes a simplyfied approach may be the better choice. In these cases factories may be an option.

Apparently MS will be providing a factory for creating your own application blocks for v3.0 of the Enterprise Library , should you desire to do so. Reading Ayende's latest post on this and his link to this flashback post from Joel Spolsky, had me rolling on the floor laughing.