I don't see a need to subclass the container.

tests involving the container are usually integration tests. making
sure i can resolve a component, or a feature works.
on the rare occasion I inject the kernel into a component I mock
IKernel.
there should be very few references to the container, so all in all
the number of tests involving the kernel/windsor should be minimal.

installers are for registering components, facilities are for
extending the functionality of the container.

On Sep 23, 9:59 am, Dru Sellers <[email protected]> wrote:
> Are there any best practices for how to use the container in your
> application?
>
> Do you subclass windsor for your application, or do you put things in
> installers.
> Do you use installers or facilities
> Do you unit test your container? And if so what does that look like.
>
> Thoughts,
> -d

-- 
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/castle-project-users?hl=en.

Reply via email to