I usually also have the Web App split in two: 1. MVCProject - controllers, filters and stuff. This has dependencies to the "Int" projects 2. MVC Web App - this has dependencies to *everything* it needs.
This is safe because in this projects there is virtually no code in the Web App project. Only views, global application class and possibly some MembershipProvider class so the risk of jeopardizing the n-tier architecture is low and deployment is a breeze There is also a second solution. You could consider merging the Impl and Int assemblies and hide implementations by having those classes internal. Configuring any mature DI is then best by using configuration modules (installers in Windsor). You could say that this causes your assemblies to rely on your DI container but let's face it, you aren't going to switch to another one during your project's lifetime with 99% certainty. And with Windsor you still can use XML configuration to override injection defaults (for example for different deployment environments or temporarily mocking not yet implemented services) I am using Monorail by the way, but that should not make much of a difference. Regards Tomasz -- 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/-/joSccmyqRRkJ. 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.
