Model Extension via MEF

I agree that this is something weird but I'm just asking the possibility of this one.

I'll try to rephrase it, the concept is like this:

We as a software provider has this set of base components of our product.

Example:

1. OurCompany.DomainModel

2. OurCompany.BusinessLayer

3. OurCompany.Forms

Where Forms makes use of BusinessLayer w/c makes use of the DomainModel for the dataaccess. (So there will be entities on that model)

Now, we have a feature of our software called ICE (Intergrated Code Expansion) so kinda plugin or so.

We are letting our customer to override some of the Forms, BusinessLayer and database schema (this is the time  that ORM is not yet existing) by inheriting them and calling the customized components instead of the base one (but in the perspective of the base application, it is just calling the default component)

The requirement of our project now is to make it ICEable, Forms and BusinessLayer has no problem and we see MEF as a way to go to do the work but our problem would be the Model. We're not giving the customer the source code of all the base components, they are just inheriting it, overriding or adding some methods, add some bindings, add some controls to the inherited form and we will call the customized one instead of the default. The problem is the Model, how can we extend the model by just inheriting it our any other Devforce approach and let BusinessLayer use the extended one rather than the default.

Thanks,

Von

Hi,

Thanks,

Von