We structure our MVC web projects in a VS2010 solution like so: 1. DLLProjectA.Int 2. DLLProjectA.Impl 3. DLLProjectB.Int 4. DLLProjectB.Impl 5. DLLProjectC.Int 6. DLLProjectC.Impl . .
N. MyMVCProject DLLProjectB may use items from DLLProjectA but only through dependency injection / interfaces. We currently register all of our castle windsor dependencies via web.config on our mvc web application. We use post build events in MyMVCProject to ensure that IMPL (implementation) projects are copied to the mvc web app's bin folder. Using post build events to copy IMPL assemblies the web app bin folder requires artificial project dependencies to make everything work properly. This can be tedious and error prone. Is there a better way to deploy IMPL assemblies to the consuming app's bin folder? Is it safe to replace post build events with direct project references from the MVC app to each of the IMPL DLL projects or does this establish tight coupling? Would like to hear what other castle windsor users are doing. thanks -- 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/-/s45A6emfEUoJ. 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.
