inversion of control - Solution-Architecture using Castle.Windsor Installers -
i've been doing quite lot of research introducing dependency injection framework organisation - better late never! far research has focussed heavily on castle.windsor. research has led me concepts such installers, interceptors (specifically logging cross-cutting concern), , facilities, of plan on using.
my question how structure solution (my project architecture in visual studio) di framework replaced @ point in future (perhaps if better comes along in 2 years time).
i'm developing framework library organisation uses common-service-locator service location, configuration of container?
if put installers in same project service implementations, front-end project need reference these projects (assuming fluent configuration) when configure container installers. these service implementations data-access-layer concerns, dont want front-end referencing specific layer (to 100% ensure no leakage of concerns).
i haven't found addressing question, i'm thinking might on wrong track line of thinking. won't offended if tell me :)
anyway, i've developed proof-of-concept whereby each of project layers (e.g. xxxorganisation.data.model.nhibernate - stores concrete implementations of specifications etc.) have corresponding dll project container-configuration-concerns such installers (e.g. xxxorganisation.data.model.nhibernate.castle). plan use ilmerge merge projects castle specific configuration 1 project, referenced front-end (web-application).
is viable approach?
in addition above, register services use incerceptors things logging. thinking castle configuration projects (containing installers) might reference xxxorganisation.aop (or xxxorganisation.castle base project) kind of thing...
i appreciate more experienced me questions, or provide me advice.
kind regards, ryan.
if writing framework or library (not same thing) shouldn't using container @ - instead, should architect support kind of dependency injection.
only applications should use di containers - composition roots.
Comments
Post a Comment