First of all look at the definition by @martinfowler "A type that acts as the supertype for all types in its layer" all you need is a Supertype Class for all the Objects. I usually use it in Repository layer as a generic Repository. I recommend to use it if you have more than one kind of object in your layer. Let's consider an example in real world , Create a class and name it Profile

  1.    public class Profile
  2.     {
  3.         public string Name { get; set; }
  4.     &n

"no client should be forced to depend on methods it does not use." Interface segregation is a Simple but useful patterns of SOLID principle , in other words interface segregation is just about splitting an interface to several interfaces to make it simple working with classes those are going to implement the members.


Suppose this interface :

  1.     public interface IAccountService
  2.     {
  3.         void CreateBankAccount();
  4.         vo

AutoMapper is an object-to-object mapper , that enable mapping objects to another objects when it is needed ,sometimes we need to Map our Model to ViewModel and vice Versa .It is very useful when you are going to Map your Model to View Model especially when you are going through MVVM or MVC pattern .

Fire Up visual studio , Create a MVC Project  and create a class with this definition  in your solution :

  1.     public class User
  2.     {<