Okay, my comments on the issue: It makes absolutely no sense to me to make separate classes, one that holds methods and function definitions and another that holds properties (not referring to the concept of partial classes).
Serialization is a fine tuned process and you can use declarative attributes to define exactly what members of a class will be serialized. On Mar 7, 10:09 am, raringsunny <[email protected]> wrote: > Hi, > > I have a question regarding the design of a class. Should the > properties of a class exist in a separate class from the methods of a > class? > > For e.g. If I have a class named "Employee". Should I make two > separate classes; one holding methods of a class such as 'Add > Employee', 'Update Employee' and 'Delete Employee' and another class > holding its properties such as 'Employee ID', 'First Name', 'Last > Name'. > > I remember working on one project where we had separate classes for an > object's properties and a separate class where all the methods of the > class were implemented in the business layer using a class library > project template. > > Please advice on what would be a most appropriate and effective > design? > > Regards, > Sunny
