I’m working on an ASP.Net website along with a supporting Class Library for my Business Logic, Data Access code, etc.
I’m EXTREMELY new and unfamiliar with the Unity Framework and Dependency Injection as a whole. However, I’ve managed to get it working by following the source code for the ASP.NET 3.5 Portal Starter Kit on codeplex. But herein lies the problem:
The Class Library is setup with Unity and several of my classes have [Dependency] attributes on their properties (I’m exclusively using property setter injections for this). However, the Global.asax is telling Unity how to handle the injections….in the Class Library.
Is this best practice or should the Class Library be handle it’s own injections so that I can re-use the library with other websites, webapps or applications? If that is indeed the case, where would the injection code go in this instance?
I’m not sure how clear the question is. Please let me know if I need to explain more.
Though not familiar with Unity (StructureMap user) The final mappings should live in the consuming application. You can have the dll you are using define those mappings, but you also want to be able to override them when needed. Like say you need an instance of IFoo, and you have one mapped in your Class Library, but you’ve added a new one to use that just lives in the website. Having the mappings defined in the site allows you to keep things loosely coupled, or else why are you using a DI container?