Home

Introduction

The recommended way to use IoC containers is that the Composition Root of the application is the only place where the container is accessed. Unfortunately many application can’t create everything at once during the application start or at the beginning of a web/wcf request because not everything is known at this moment. These applications need a way to create new instances using the kernel at a later time. Preferably this is done without introducing a reference to the container. This is where factories come into play. Instead of injecting the kernel into classes that need to create new instances we inject a factory. This factory is responsible to create the new instances using the kernel. There are two ways to implement such a factory: A factory interface and as a Func or Lazy. Both ways are covered by this extension.

Binaries

• Latest build: http://teamcity.codebetter.com/viewLog.html?buildTypeId=bt293&buildId=lastSuccessful&tab=artifact

Documentation:

• Factory Interface
• Factory Interface - Named Bindings
• Factory Interface - custom instance provider
• Func
• Lazy