Hello,

I was wondering if it's possible to add "Additional Interfaces" per group. AFAIK it's only possible to set at the project level (for all entities) or at the entity level, and not at group level.

I'm using LLBLGen v3.5

Kind regards, Sven.

Do you need to define an interface to be inherited by each element (e.g. entity) within a group?

As you said, currently it's either on the project level, or per element (e.g. entity).

Yes, our DB is split up into multiple schemas (Core, Security, moduleA, moduleB,...)

For FDA compliance, we added audit trailing and have chosen to have 1 audittable per table, in audit schema'ss (AuditCore, AuditSecurity,...). The auditing is handled in an override of OnSaveEntityComplete of the DataAccessAdapter (only a few lines of code, and since we don't to Deletes, it's the simplest approach). The implementation needs us to have an IAuditable interface on all entities (except of course on the Audit-entities themselves)

Different schema's result into different groups per default in the designer. It would be very handy to be able to define the IAuditable interfaces at the group level. The options now are : - at project level : not good, our audit-entities then also are IAuditable - at entity level : has to be added for hundreds of entities, a boring and error-prone work

As a matter of fact, what is the intention of splitting up in groups in the designer ? I don't see any benefits (no other namespaces, no "customization" at group level) except for the visualization in the designer (which is already nice of course

Kind regards, Sven.

HcD wrote:

Yes, our DB is split up into multiple schemas (Core, Security, moduleA, moduleB,...)

For FDA compliance, we added audit trailing and have chosen to have 1 audittable per table, in audit schema'ss (AuditCore, AuditSecurity,...). The auditing is handled in an override of OnSaveEntityComplete of the DataAccessAdapter (only a few lines of code, and since we don't to Deletes, it's the simplest approach). The implementation needs us to have an IAuditable interface on all entities (except of course on the Audit-entities themselves)

Different schema's result into different groups per default in the designer. It would be very handy to be able to define the IAuditable interfaces at the group level. The options now are : - at project level : not good, our audit-entities then also are IAuditable - at entity level : has to be added for hundreds of entities, a boring and error-prone work

Good suggestion, we'll look into it for v4.x

In the mean time, it might be better to add this through a plugin, which shouldn't be too hard.

As a matter of fact, what is the intention of splitting up in groups in the designer ? I don't see any benefits (no other namespaces, no "customization" at group level) except for the visualization in the designer (which is already nice of course Kind regards, Sven.

See: http://weblogs.asp.net/fbouma/archive/2012/06/20/llblgen-pro-feature-highlights-grouping-model-elements.aspx

Implemented in v4 using the same rules system as with attributes, so fine-grained support elements get which interfaces/namespaces

You rock !