It's a tough problem.. One thing you could try is to check during setup if the facility you need is already installed and either throw an exception if it's not, or install it yourself..
thoughts? On Sun, Apr 29, 2012 at 7:53 AM, Anthony Johnston <[email protected]> wrote: > ok.. what about an attribute? > > or am I missing a trick? > > On Apr 18, 2:14 pm, MrAntix <[email protected]> wrote: >> Setting up Installers for reuse along side a component which may or >> may not required facilities and may in fact require the same ones.. >> >> but installers have no way of declaring which facilities they use, and >> addfacility will fail if one exists, although I can check >> >> so was thinking, would it be good to have the facilities required >> declared with the installer? >> >> interface IWindsorInstaller<TFacility1, TFacility2> : >> IWindsorInstaller >> >> Windsor could determine whether or not its already added >> >> Could use the same pattern as Tuple for the type parameters or a Tuple >> its-self? >> >> interface IWindsorInstaller<Tuple> : IWindsorInstaller >> >> so.. >> >> public class SomeServiceInstaller : >> IWindsorInstaller<Tuple<TypedFactoryFacility, MyFacility>> > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" 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-devel?hl=en. > -- Cheers, hammett http://hammett.castleproject.org/ -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en.
