best practice using method in a class - class

Question

Suppose I have Employee class, should I put in the Employee class the add, delete, view, etc. methods? or should that class only for the getter/setter class?
which is better/acceptable/best practice?
Employee
-------------------
+int id (get/set)
+string name (get/set) (methods are called in another class)
Employee
-------------------
+int id (get/set)
+string name (get/set)
-add employee
-remove employee

Answer 1

This comes down to separation of concerns
When you are deciding these things, you need to use your intuition and think about it logically. What concerns an employee.
You have a class called Employee, then include in the Employee class everything that concerns an Employee. It doesn't make sense for an employee to be able to Add and Remove Employees to themselves. Maybe what you are looking for there is a class of Employees (plural) that will manage your employees ect ect ect.
But your Employee "will" have Name and Id and other things that concern it.
The goal here is to break up your concepts in to concrete real world concerns as much as possible, it makes it much easier to understand a design if you do

Answer 2

Assuming you have a database behind:
For similar purposes I have a base class for all entities that takes care of CRUD functionality and the ID. All entities inherit from this base class and take care of individual properties, like name, address, etc.
Also I have collections of all entities of the same type that manage the items in it.

Answer 3

Short Answer: Go with option 2
If you consider the separations of concerns, you should have an Employee to track the information of a single person and an Employee Repository for managing all of your employees. What makes up an record should be independent from how the record is stored/queried.

Answer 4

Employee class has information of employee, and the methods of employee. Looks like you are trying to maintain a collection of employees (assuming from add, delete employee requirement)
In that case add,delete,remove are not the responsibilities of employee class, rather the collection of employees.
Read on the OOP principles.

Answer 5

First 5 Principles of Object Oriented Design(S.O.L.I.D).
After Employee
public class Employee :ViewModelBase, IEditableObject
{
public int EmployeeID { get; set; }
public string FullName
{
get
{
return $"{this.Name} {this.Surname}";
}
}
private string _Name;
public string Name
{
get { return _Name; }
set
{
_Name = value;
OnPropertyChanged("Name");
}
}
}
After Create a Generics class with Repository For managment Add,Delete,Update etc...
public interface IRepository<T> where TEntity : class
{
IEnumerable<TEntity> GetUsers();
IQueryable<TEntity> SearchFor(Expression<Func<TEntity, bool>> predicate);
TEntity GetById(int id);
void Save(TEntity model);
void Delete(int id);
}
And Employee Base implementation Repository
public Class EmployeeManager : Repository<Employee>
{
public IEnumerable<TEntity> GetUsers()
{
//your code
}
public IQueryable<TEntity> SearchFor(Expression<Func<TEntity, bool>> predicate)
{
//your code
}
public TEntity GetById(int id)
{
//your code
}
public void Save(TEntity model)
{
//your code
}
public void Delete(int id)
{
//your code
}
public void DeleteAll(Employee[] employees)
{
//your code
}
}
Unity Repository Best Practices

Answer 6

I think you should have all the tools you need in one class, have multiple constructors to help load only the info as needed.