<PackageReference Include="Castle.Windsor" Version="5.0.0-beta001" />

IKernelEvents

public interface IKernelEvents
Summary description for IKernelEvents.

Event fired when the kernel was added as child of another kernel.

Event fired before the component is created.

Event fired when a component instance destroyed.

Event fired after the ComponentModel is created. Allows customizations that may affect the handler.

Event fired when a new component is registered on the kernel.

Event fired when a dependency is being resolved, it allows the dependency to be changed, but the client ComponentModel must not be changed.

Event fired when a collection is being resolved (via ResolveAll or another overload) and the collection is empty. Implementors would usually log that fact or potentially throw an exception (especially in development).

Event fired when a new handler is registered (it might be in a valid or waiting dependency state)

Event fired when a new handler is registered (it might be in a valid or waiting dependency state)

Event fired when registration / installation process is completed. That is when container is about to exit Register method. This event is raised once regardless of how many components were registered. If the Register is called by Install the event is raised when that method exits.

Event fired when the kernel was removed from being a child of another kernel.