I wouldn't see value in having installers depend on other installers.
the point is that each is an atomic unit. if you have dependent
components, then i would register them in a single installer or
encapsulate it within a facility.
you can have a facility register additional facilities.
void Init()
{
Kernel.AddFacility<Other>().Regsiter(...);
}
On Nov 24, 9:33 am, Dru Sellers <[email protected]> wrote:
> Is there any way to have the installer require other installers?
>
> or facilities?
>
> At work we have carved up a lot of common code into various installers, and
> I was hoping that instead of developers getting a missing component, they
> could get a missing facility/installer error
>
> -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.
