Khurram wrote:
Thanks for the response. So It means I have to use MyEntityNameEntity for everything rather EntityNameEntity.
In theory, yes, but it's up to you. The base entity contains all you need to work, but if you have custom properties/methods/etc in the derived class, then you should use the derived class.
Khurram wrote:
Actually previously I was using EntityNameEntity classes to bind to controls or grids. Now in 2 preset I need to bind with MyEntityNameEntity.
Yes.
Khurram wrote:
If I am not wrong any business logic require for this entity will go to MyEntityNameEntity and because it inherits from EntityNameEntity it is also the same thing ?
Yes
Khurram wrote:
Kindly describe if I am conceptually wrong here.
My advice is: is you don't really need a derived class, don't use it, use the normal preset. I have worked many projects with no need of TwoClasses preset. If I need some custom code I add it to a partial class of the entity, that way I always use the same class. Also, in Adapter is more natural to put the business logic is some other kind of Business/Manager/Service classes, so the only custom code I have in entity partial classes is for custom properties and some methods related to the data inside the entity, not the logic of the business process.
But, for some people the TwoClasses preset is very helpful, that why it's there.