**>>I pressume you're mainly interested in the values of the fields ? **
Well user values and user methods. 90% of the time people will not need the lower level LLBLGen properties/methods.
>>The members won't go away as they're public properties of the class.
Oh yes they will
Consider a class generated called CategoriesEntity.
If I were LLBLGen I could have simply named this class CategoriesEntityBase, and then generated a derived class like this:
class CategoriesEntity : CategoriesEntityBase
{
public CategoriesEntity() {}
public int CategoryName // plus other user data and user methods
{
get { return base.CategoryName; }
}
}
Now an instance of this class could be created like this:
var cleanEntity = new CategoriesEntity();
Then when viewing cleanEntity in the debugger you will see only this beautiful sight:
cleanEntity
+base
CategoryName
So this is one way it could be done with no interface or client or performance implications.
I think the other poster is correct that it can also be done via decorations, but I haven't researched the syntax of that approach.
Regards,
LTG