S.O.L.I.D PRINCIPLES TO DESIGN CLASS IN ASP.NET C#

S.O.L.I.D PRINCIPLES TO DESIGN  CLASS IN ASP.NET C# 

(CONCEPT OF OOPS)

• The Single Responsibility Principle :  THERE SHOULD NEVER BE MORE THAN ONE REASON FOR A CLASS TO CHANGE.

• The Open Closed Principle : SOFTWARE ENTITIES (CLASSES, MODULES, FUNCTIONS, ETC.) SHOULD BE OPEN FOR EXTENSION, BUT CLOSED FOR MODIFICATION. 

• The Liskov Substitution Principle :   FUNCTIONS THAT USE POINTERS OR REFERENCES TO BASE CLASSES MUST BE ABLE TO USE OBJECTS OF DERIVED CLASSES WITHOUT KNOWING IT.

• The Interface Segregation Principle: CLIENTS SHOULD NOT BE FORCED TO DEPEND UPON INTERFACES THAT THEY DO NOT USE.

• The Dependency Inversion Principle :  HIGH LEVEL MODULES SHOULD NOT DEPEND UPON LOW LEVEL MODULES. BOTH SHOULD DEPEND UPON ABSTRACTIONS

THIS IS THE MOST IMPORTANT INTERVIEW QUESTION IN ASP.NET C#