Does that answer the question? http://kozmic.pl/2010/08/10/ioc-patterns-ndash-partitioning-registration/
-- Krzysztof Kozmic On Wednesday, 12 September 2012 at 9:37 AM, Scott_M wrote: > We are writing a .NET 4.5 WCF service hosted as a Windows NT service and plan > to use latest castle windsor / wcf facility for dependency injection. The > WCF service will have multiple dependencies: > > 1. Business Logic Components (INT and IMPL assemblies) > 2. Data Access Layer Components (INT and IMPL assemblies) > 3. Logging Components (INT and IMPL assemblies) > 4. Various utilities (INT and IMPL assemblies) > > For component registration, we have used xml configuration for similar > projects in the past. However, this was slow, tedious, fragile, and not very > re-usable for subsequent projects. What is best practice for structuring > installers for a project of this nature? Do you write one giant installer > project to cover 1-4? Do you write separate installers for each assembly > implementation? How do you deal with installer dependencies so they are > installed in the proper order? How do you prevent from installing a > component twice? > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/castle-project-users/-/iVTa2_kh6DkJ. > To post to this group, send email to [email protected] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/castle-project-users?hl=en. -- 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.
