Typed Factory Facility provides automatically generated Abstract Factories that you can use to create components in your code, while still remaining agnostic to the presence of the container. It is part of Castle.Windsor.dll.
ℹ️ Typed factories vs alternatives: Use typed factories wherever you need to pull something from the container. Alternative approaches, like Service Locator, or referencing the container directly are both inferior to typed factories and should be avoided. See this post for more in-depth discussion.
All the following code samples will assume that the following variable is in scope
IKernel kernel = new DefaultKernel();This will obviously also work if you use IWindsorContainer instead
IWindsorContainer container = new WindsorContainer();Preferable way of working with the container is to have the container inject all the required dependencies upon creation of the object. There are some scenarios where an object needs to have other objects supplied to it after it was created, for example to handle some external event. In this case the object needs to pull its dependencies. Best way to do it is to use a factory that will supply the objects as requested. Typed Factory Facility implements the factories for you (under interface you provide) and supplies instances to you from the container.
Typed Factory Facility provides two distinct kinds of factories: interface-based and delegate-based. Notice that there are quite a lot of differences between how they work.
ℹ️ Prefer interface-based factories: It is strongly suggested to use interface-based factories. They are more powerful, cover wider range of scenarios and give you ability to release your components.
To use the facility you have to register it with the container. You need the appropriate namespace in scope:
using Castle.Facilities.TypedFactory;Then you can register the facility with the container
kernel.AddFacility<TypedFactoryFacility>();