Blue Theme Orange Theme Green Theme Red Theme
 
Home | Forums | Videos | Advertise | Certifications | Downloads | Blogs | Interviews | Jobs | Beginners | Training
 | Consulting  
Submit an Article Submit a Blog 
 Jump to
Skip Navigation Links
TechnologyExpand Technology
WebsiteExpand Website
Team Foundation Server Hosting
Search :       Advanced Search »
Home » Design & Architecture » Wrapper Patterns in C#, Part IV: The Adapter Pattern

Wrapper Patterns in C#, Part IV: The Adapter Pattern

In this series of four articles, we will travel down the C# rabbit hole and see how it is all possible with some wrapper patterns: Proxy, Decorator, and Adapter.

Author Rank :
Page Views : 27370
Downloads : 358
Rating :
 Rate it
Level : Intermediate
   Print Read/Post comments Post a comment  Similar Articles  
   Email to a friend  Bookmark  Author's other articles  
Download Files:
Adapter.zip
 
 
6 Months Free & No Setup Fees ASP.NET Hosting!
Become a Sponsor
6 Months Free & No Setup Fees ASP.NET Hosting!
Become a Sponsor
 Tag Cloud
 Latest Jobs
More ... 
 Latest Interview Questions
More ... 

Did you ever wish for a superhuman power to be impervious to bullets or travel outside your body? How about the superpower to be able to breathe underwater or fly?   Or how about a changing the way you look so you can disguise yourself as anyone, or anything?  In this series of four articles, we will travel down the C# rabbit hole and see how it is all possible with some wrapper patterns: Proxy, Decorator, and Adapter. 

Part IV. The Adapter

In our journey through this series we learned how to manifest superpowers with two wrapper-type GOF design patterns.  In part II we looked at the Proxy pattern to reveal protection powers.  In part III we looked at the Decorator to add functional powers.  In this final section we are going to look at the Adapter pattern to see how to implement morphing powers.

Let's start with an INormalDude contract...

public interface INormalDude

{

          string Name { get; set; }

          void Eat();

          void Talk();

}

...and the NormalDude class:

public class NormalDude : INormalDude

{

          private string m_name;

          private string m_thingToSay;

          public string ThingToSay

          {

                    get { return m_thingToSay; }

                    set { m_thingToSay = value; }

          }

          #region INormalDude Members

          public string Name

          {

                    get { return m_name; }

                    set { m_name = value; }

          }

          public void Eat()

          {

                    Console.WriteLine(string.Format("{0}: Please pass the mayo.", m_name));

          }

          public void Talk()

          {

                    Console.WriteLine(string.Format("{0}: {1}", m_name, m_thingToSay));

          }

          #endregion

}


Using our C# wrapping powers we will give our NormalDude the superpower to morph so that wolves think that he is one of them.

Here is our IWolf contract...

public interface IWolf

{

          string FoodSource { get; set; }

          void Devour();

          void Howl();

}

...and the Wolf class:

public class Wolf : IWolf

{

          private string m_foodSource;

          #region IWolf Members

          public string FoodSource

          {

                    get { return m_foodSource; }

                    set { m_foodSource = value; }

          }

          public void Devour()

          {

                    Console.WriteLine(string.Format("Wolf: This wolf is devouring {0}.", m_foodSource));

          }

          public void Howl()

          {

                    Console.WriteLine("Wolf: Aaaaaaaaaaaarrrrrrrrrrrooooooooooooo!");

          }

          #endregion

}

Now we need to wrap our Normal dude so that he implements the IWolf interface.  Do you see how we are wrapping the NormalDude in the code below and then expressing some of his functionality through the IWolf interface?

public class DudeWolfAdapter : INormalDude, IWolf

{

          private INormalDude m_dude;

          private string m_foodSource;

          public DudeWolfAdapter(INormalDude dude)

          {

          m_dude = dude;

          }

          #region INormalDude Members

          public string Name

          {

                    get { return m_dude.Name; }

                    set { m_dude.Name = value; }

          }

          public void Eat()

          {

                    m_dude.Eat();

          }

          public void Talk()

          {

                    m_dude.Talk();

          }

          #endregion

          #region IWolf Members

          public string FoodSource

          {

                    get { return m_foodSource; }

                    set { m_foodSource = value; }

          }

          public void Devour()

          {

                    m_dude.Eat();

                    Console.WriteLine(string.Format("{0}: Is there any way we can get this cooked?", Name));

          }

          public void Howl()

          {

                    m_dude.Talk();

          }

          #endregion

}

Here are our results:

In Conclusion

Although Super Bill has not quite adapted the social graces required by the pack, he can still blend in. This sample show us how we can use our C# wrapping powers to change the way objects look so we can disguise them as anything.

Wrap Up

The three patterns we looked at all utilize a basic wrapping pattern and are pretty much the same except for the functionality they provide.

The Proxy is a wrapper that limits access to an object or can be utilized as a stand-in to be used in place of the object.  The Decorator is a wrapper that adds additional functionality to an object.  And finally, the Adapter is a wrapper that helps one object integrate with any other object's interface.

One thing we need to be careful of is to only use wrappers where they are needed because our code can become increasingly complex and difficult to maintain (especially by other more junior developers from non OOP backgrounds who don't fully understand patterns).  We should always look at all the ways we have to give our objects super powers.   If there is a simpler way to achieve the same result, it is probably a better route to take.
 
I hope you enjoyed this series and have a better understanding of wrappers and specifically the Proxy, Decorator, and Adapter patterns.

Until next time,

-Only use your powers for good

Comment Request!
Thank you for reading this post. Please post your feedback, question, or comments about this post Here.
Login to add your contents and source code to this article
 [Top] Rate this article
 
 About the author
 
Matthew Cochran
Looking for C# Consulting?
C# Consulting is founded in 2002 by the founders of C# Corner. Unlike a traditional consulting company, our consultants are well-known experts in .NET and many of them are MVPs, authors, and trainers. We specialize in Microsoft .NET development and utilize Agile Development and Extreme Programming practices to provide fast pace quick turnaround results. Our software development model is a mix of Agile Development, traditional SDLC, and Waterfall models.
Click here to learn more about C# Consulting.
 
Introducing MaxV - one click. infinite control. Hyper-V Hosting from MaximumASP.
Finally – a virtual platform that delivers next-generation Windows Server 2008 Hyper-V virtualization technology from a managed hosting partner you can truly depend on. Visit www.maximumasp.com/max for a FREE 30 day trial. Hurry offer ends soon. Climb aboard the MaxV platform and take advantage of High Availability, Intelligent Monitoring, Recurrent Backups, and Scalability – with no hassle or hidden fees. As a managed hosting partner focused solely on Microsoft technologies since 2000, MaximumASP is uniquely qualified to provide the superior support that our business is built on. Unparalleled expertise with Microsoft technologies lead to working directly with Microsoft as first to offer IIS 7 and SQL 2008 betas in a hosted environment; partnering in the Go Live Program for Hyper-V; and product co-launches built on WS 2008 with Hyper-V technology.
Dynamic PDF
ceTE software specializes in components for dynamic PDF generation and manipulation. The DynamicPDF™ product line allows you to dynamically generate PDF documents, merge PDF documents and new content to existing PDF documents from within your applications.
Discover the Top 5 .NET Memory Management Fundamentals
To write the best .NET code, you need to know exactly how the .NET framework really manages memory. Ricky Leeks presents the Top 5 fundamental facts of .NET memory management. Learn more.
Nevron Chart for .NET 2010.1 Now Available
The leading .NET charting control now features PDF, Flash and Silverlight export, visualization of large datasets and more. Deliver true charting functionality to your BI, Scorecard, Presentation or Scientific apps. Download evaluation now.
ASP.NET 4 Hosting
Get 2 Months Free of ASP.NET Hosting for Only $4.95/month! Receive FREE MS SQL and MySQL Databases Including ASP.NET 4/3.5, MVC 3.0, Silverlight 4, Windows 2008/IIS 7.0 Plus FREE IIS 7 Modules. Host UNLIMITED ASP.NET Web Sites – Click Here!
 
 Post a Feedback, Comment, or Question about this article
Subject:
Comment:
Discover the top 5 tips for understanding .NET Interop
Become a Sponsor
 Comments
? by Felipe On May 23, 2007
Where's the code for that last result window?
Reply | Email | Modify 
Team Foundation Server Hosting
 © 2012  contents copyright of their authors. Rest everything copyright Mindcracker. All rights reserved.