Chain of Responsibility Design Pattern - Course C# 4.0 - Lesson 19 | .net courses

Duration:  18 minutes

Summary: Design patterns are important because they represent generic solution to a common problem. They are created in a way that solves the common task at hand, but more importantly provide a solution that is easier to maintain and enhance as the application evolves. Please note that the code I am covering in these examples is mostly from the DoFactory web site (not my own). I am covering these patterns to make developers aware of them and encourage everyone to find the pattern that matches his/her needs and apply it to a specific scenario. Please note that not every problem needs a pattern (in other words, do not over use them). Some patterns are similar; with experience you can hand pick the one that mostly suits your needs. In this case, we will cover the Chain of Responsibility Design Pattern. This pattern avoids coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.

Methodology of the development of example: Good coding standard and simplified design.

Technology Used: C# 4.0

Keywords: C#, System, Console, abstract, override, ReadLine, WriteLine, protected, foreach, GetType().