entity/field custom properties hashtable... uses?

Posts   
 
    
jmeckley
User
Posts: 403
Joined: 05-Jul-2006
# Posted on: 26-Jan-2007 23:37:47   

I am trying to understand the purose of the custom properties hashtable. The documentation gives the example of SqlServer Extended Properties. I have worked with MSSQL for a few years and haven't encountered extended properties. granted my projects are small to medium sizes apps so maybe I haven't had a need for this.

searching the forums it seems references to custom properties relates to extending properties within entities, not the custom properties hastable.

After some brainstorming the only example I cam up with was meta-data for the entity/field. Like storing a desciption of the entity, or the display text (label) for a field. Maybe in some crude way simple validation rules could be stored here like string length or min/max date/number values which could then be extracted and parsed during field/entity validation calls. but since these values are consturcted at buildtime and not runtime why not just write them into the validation code instead of parsing them from the hashtable? Again, just thinking outloud.

would anyone be willing to provide examples/scenarios where they have used this feature?

Thank you,

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39848
Joined: 17-Aug-2003
# Posted on: 27-Jan-2007 08:39:48   

Descriptions of fields, but also meta-data which is used by templates at code generation time. For example, the GUI templates we now have in beta use custom properties to control the output.

Also, some people use them to decide which control to show at runtime with dynamic build UI's. I don't think custom properties are usable for validation rules.

Frans Bouma | Lead developer LLBLGen Pro
jmeckley
User
Posts: 403
Joined: 05-Jul-2006
# Posted on: 27-Jan-2007 17:59:03   

thank you, that helps clear things up for me. I'll take a look at the GUI templates for further clairification.