Arguments

 Burden

 CircularDependencyException

 ComponentNotFoundException

 ComponentReference`1

 ComponentRegistrationException

 ComponentResolutionException

 DefaultKernel

 InstanceReference`1

 KernelException

 HandlerState

 AbstractSubSystem

 SubSystemConstants

 IComponentActivator

 IComponentModelBuilder

 IDependencyResolver

 IFacility

 IHandler Contract for the IHandler, which manages an component state and coordinates its creation and destruction (dispatching to activators, lifestyle managers)

 IHandlerFactory Extension point to allow the developer to use his implementation of

 IHandlerSelector Implementors of this interface allow to extend the way the container perform component resolution based on some application specific business logic.

 IHandlersFilter Implementation of this interface allows for extension of the way the container looks up multiple handlers. It provides the necessary hook to allow for business logic to prioritize, filter, and sort handlers when resolving multiple handlers.

 IKernel The IKernel interface exposes all the functionality the MicroKernel implements.

 IKernelEvents Summary description for IKernelEvents.

 IKernelInternal Extended contract of kernel, used internally.

 ILifestyleManager The ILifestyleManager implements a strategy for a given lifestyle, like singleton, per-thread and transient.

 IProxyFactory Defines the contract used by the kernel to obtain proxies for components. The implementor must return a proxied instance that dispatch the invocation to the registered interceptors in the model

 IProxyFactoryExtension

 IReference`1 Represents obtained just in time object.

 IReleasePolicy Policy managing lifetime of components, and in particular their release process.

 ISubDependencyResolver Implementors should use a strategy to obtain valid references to properties and/or services requested in the dependency model.

 ISubSystem A subsystem is used by the MicroKernel to deal with a specific concern.