Hi folks,
I'm working on an application framework that is supposed to be mostly modular, meaning once the framework is done, all business intelligence is incorporated in plugins that can be included via config.
Most modules have the common aspect that they use NHibernate to access a database, and often they use the same tables.
What I do now is create an assembly for every used DB-Schema and create the mappings per module, so that ModuleA can define mappings completely independent from those defined by ModuleB. That leads to some redundancy, but helps keeping this autonomous.
A colleague of mine moaned about this, saying that the mappings should be defined in the assembly that holds the mappings, but that would mean dependencies across the model assemblies, which are the reason why I intend to switch from MappingAttributes to MappingXML...
What do you guys think about this?