Thank for reply! As always, you are very helpful!
Understood Edition/feature mechanism, good clarification!
About multiple DbContext, I know and tried that ... but in my scenario modules can refer to entity of other module. Using separate DbContext whit different ContextKey make EF to "recreate" table mapped to entity in referenced assembly.
And this is not good!
I'm approaching to as system that can provide verticalized solution when needed.
For example, if I have developed a module for managing contacts, and I have two customer that can use this module, simply start from AspNetBoilerPlate template, add my own nuget package and that's all!
This maybe sound strange, but is commonly in our "customer habitat" where they want own server inside their office ... because they feel more secure.... mah... I never understand this thoughts!
So finally I'm imaging a separate ABP modules that are able to manage their own migrations, and concur to one big application-per-customer based on their needs.
Thanks for reply! When .net core will be supported, I'll be very happy!
