Are Custom Columns/Tables Supported by AOP Automatically?

[Ying]

For ORM classes, it is common to add custom columns, even tables after deployment. I do know OpenAccess has artificial fields and types. But artificial fields/types are different with pre-defined ones, especially when you want to use LINQ on them.

I know OpenAccess has some AOP function built in. For OpenAccess supports for legacy database schemes, it should be very easy to extend ORM classes by adding extra corresponding properties, even extra corresponding classes at RUN TIME, at least before loading, by the help of AOP. I mean without touch to any source code at loading time or at run time.

In other words, the entity classes can be upgraded at run time without touch the source code. One scenario is I won't release source code to clients, but allow them to extend the database model(tables and columns) after deployment.

I searched this website and the manual and I couldn't find this feature.

Can someone confirm it? Of course, it is better to show how to do it.

Thank you in advance,

Ying

[Damyan Bogoev]

Hi Ying,

In this case the only approach you could use is the Artificial Fields mechanism. The Enhancer should be aware of all changes made to the model in runtime and this can be achieved only with artificial fields.

Greetings,
Damyan Bogoev
the Telerik team