Kudchikarsk.com Website Review

The Adapter design pattern is one of the most common, and most useful patterns available to us as software developers. When you have a clas* that needs to utilize a particular interface, and you have a library that includes the functionality you need, but it doesn’t use the interface that you require. You can achieve the reuse of that library’s code by creating an Adapter clas* that sits between your client code, and the code that’s in this library, and adapts one interface to the other. within this example are the Client, and the Adaptee, shown above. The Client needs some of the logic that exists within the Adaptee. Specifically, there is this AdaptedOperation that has the code that the Client wants to be able to utilize. Unfortunately, the Client has been written in such a way that it cannot directly call this AdaptedOperation because its interface is not the one that the Client expects. This is where the Adapter Pattern comes into play. The Adapter interface is created, exposing an Operation that has the interface the Client expects. For each different implementation required, at a minimum, one, its different ConcreteAdapter is created that takes that Operation and implements it, such that that code calls the AdaptedOperation. In this way, the Client will now be able to call the Operation on the ConcreteAdapter, which in turn will call the AdaptedOperation on the Adaptee. The Client really wants to use the Adaptee directly, but unfortunately it can’t due to the incompatible interface. The Adapter Pattern is simply allowing us to achieve this despite this incompatibility.     public FrenchPersonAdapter(IFrenchPerson frenchPerson)     {         this.frenchPerson = frenchPerson;     }         get { return frenchPerson.Nom; }         set { frenchPerson.Nom = value; } var service = new PersonService(); var person = new Person(); service.PrintName(person); service.PrintName(new FrenchPersonAdapter(frenchPerson));