This question is locked. New answers and comments are not allowed.
Good morning,
I am currently evaluating OpenAccess for an internally used product where we will have extensibility built in in regards of certain types. Basically we have 'Projects', and each project can have a list if IProjectElements, and the default implementations will be extended by 'plugins' so that other business units can provide and use their own elements.
Now from an extensbility point of view this works perfectly fine with MEF, but I am not sure about the (OpenAccess) persistence part. Up until now we are/were using an oodbms system and adding new assemblies 'just worked' because the oodb picked them up and stored the new object graph & instances 'natively', but how do I do that with OpenAccess where I have to specify the mapping sort of upfront. I also don't want to transport the OpenAccess dependency into each single extension so I'll probably introduce my own 'store this class & these and that properties/fields'-attributes, but can I tell OpenAccess during runtime which classes/fields etc have been added and/or what do I have to do to dynamically change/update the persistence layer via OpenAccess? Is there any way to hook into that?
Just doing a far away 'can do with reasonable amount of efforts'-check here... any experiences/ideas/suggestions?
Cheers and thanks,
-J