Probably because I havent worked with llblgen in a while I'm puzzled by this. Why are the properties of an entity object scoped as virtual (Adapter Scenario). Doesnt that mean I have to implement them as public somewhere else to be able to see them or what am I missing? Its not a beta issue it?

The virtual keyword is used to modify a method, property, indexer or event declaration, and allow it to be overridden in a derived class. So these properties can have a different implementation in derived classes.

Thank you for that. I had no idea! But seriously - what is the intent in making the properties virtual? Frans - feel free to jum in. Is the idea to build a 2 class scenario as a best practice? I remember about a year or two ago there was a discussion of that approach possibly being the best.

As Brian (bclubb) says: to have them virtual, you can have a derived class and override them in that derived class and change hte meaning of the property or add code to the property via that override

Ok - it seems I'm not expressing myself properly. Let me go and get more coffee ... In the meantime thanks .

thomas wrote:

Probably because I havent worked with llblgen in a while I'm puzzled by this. Why are the properties of an entity object scoped as virtual (Adapter Scenario). Doesnt that mean I have to implement them as public somewhere else to be able to see them or what am I missing? Its not a beta issue it?

Are you possibly thinking of "override"?

[Edit] Yuck! I meant to say "abstract".