SOLID in C# - The Interface Segregation Principle

What Is This Principle? The Interface Segregation Principle [http://en.wikipedia.org/wiki/Interface_segregation_principle] states that no client code object should be forced to depend on methods it does not use. Basically, each code object should only implement what it needs, and not be required to implement anything

SOLID in C#: The Liskov Substitution Principle

What Is This Principle? The Liskov Substitution Principle [http://en.wikipedia.org/wiki/Liskov_substitution_principle](LSP), named for and originally defined by Barbara Liskov [http://en.wikipedia.org/wiki/Barbara_Liskov], states that we should be able to treat a child class as though it were the parent class.

SOLID in C#: The Open/Closed Principle

What Is This Principle? The Open/Closed Principle [http://en.wikipedia.org/wiki/Open/closed_principle], as originally formulated by Bertrand Meyer [http://en.wikipedia.org/wiki/Bertrand_Meyer], states that a given software entity should be open for extension, but closed for modification. Essentially, any given class (or module,

SOLID in C#: The Single Responsibility Principle

What Is This Principle? The Single Responsibility Principle [http://en.wikipedia.org/wiki/Single_responsibility_principle] (SRP) states that any class must have one, and only one, reason to change. If a class has more than one reason to change, it should be refactored. Benefits The primary benefit the Single-Responsibility