Blue Theme Orange Theme Green Theme Red Theme
 
6 Months Free & No Setup Fees ASP.NET Hosting!
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
6 Months Free & No Setup Fees ASP.NET Hosting!
Search :       Advanced Search »
Home » ADO.NET & Database » Consolidate Your Binding Code

Consolidate Your Binding Code

I've noticed that in data driven UI projects there is often lots of repeated code wherever there is data binding. In this article we'll look at consolidating all the binding code in a helper class to make projects much easier to maintain by reducing the amount of code we have to dig through.

Author Rank :
Page Views : 5729
Downloads : 126
Rating :
 Rate it
Level : Beginner
   Print Read/Post comments Post a comment  Similar Articles  
   Email to a friend  Bookmark  Author's other articles  
Download Files:
BindingConsolidationSample.zip
 
 
DevExpress Free UI Controls
Become a Sponsor
 Tag Cloud
 Latest Jobs
More ... 
 Latest Interview Questions
More ... 

For this demo, we'll be using a very simple business object:

And a factory class to build our business objects:

Noisy Example:

What we sometimes run across in the UI code-behind is something that looks like this:

public partial class _Default : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        if (!IsPostBack)
        {
            IEnumerable<BizObject> source = BizObjectFactory.GetAll();

            myCheckBox.DataSource = source;
            myCheckBox.DataTextField = "Value";
            myCheckBox.DataValueField = "Key";
            myCheckBox.DataBind();

            myDropDown.DataSource = source;
            myDropDown.DataTextField = "Value";
            myDropDown.DataValueField = "Key";
            myDropDown.DataBind();

            myBulletedList.DataSource = source;
            myBulletedList.DataTextField = "Value";
            myBulletedList.DataValueField = "Key";
            myBulletedList.DataBind();

            myListBox.DataSource = source;
            myListBox.DataTextField = "Value";
            myListBox.DataValueField = "Key";
            myListBox.DataBind();

            myRadioButtonList.DataSource = source;
            myRadioButtonList.DataTextField = "Value";
            myRadioButtonList.DataValueField = "Key";
            myRadioButtonList.DataBind();
        }
    }
}

The thing that we should be screaming right about now is "Gadzooks! Look at all the repetition!".  Most likely all the other pages with binding in the project will look similar to this one so it'll be a lot of code to look through when something has to change.  

Solution 1:

In order to keep things more concise and manageable, what we should do is separate out the responsibility for binding to a simple generic helper class as follows.

public static class Binder
{
    public static void Bind<T>(ListControl target, IEnumerable<T> source, String dataTextField, String dataValueField)
    {
        target.DataSource = source;
        target.DataTextField = dataTextField;
        target.DataValueField = dataValueField;
        target.DataBind();
    }
} 

Since we have coded our helper class to the base ListControl class and the interface (IEnumerable<T>) we can use this same code for binding almost any type of collection with all the following objects.

  • BulletedList
  • CheckBoxList
  • DropDownList
  • ListBox
  • RadioButtonList

This will greatly simplify our calls and reduce our binding code throughout our project by about 75% (we went from four lines to one line).  Now our binding code looks like this:

public partial class _Default : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        if (!IsPostBack)
        {
            IEnumerable<BizObject> source = BizObjectFactory.GetAll();

            Binder.Bind(myCheckBox, source, "Value", "Key");
            Binder.Bind(myDropDown, source, "Value", "Key");
            Binder.Bind(myBulletedList, source, "Value", "Key");
            Binder.Bind(myListBox, source, "Value", "Key");
            Binder.Bind(myRadioButtonList, source, "Value", "Key");
        }
    }
}

Which would you rather maintain?

Solution 2:

Better yet, if we always want to bind to the same key and value for a specific type of object, we can simplify this further by overloading the Binder.Bind() method as follows.

public static class Binder
{
    public static void Bind(ListControl target, IEnumerable<BizObject> source)
    {
        Bind(target, source, "Value", "Key");
    }

    public static void Bind<T>(ListControl target, IEnumerable<T> source, String dataTextField, String dataValueField)
    {
        target.DataSource = source;
        target.DataTextField = dataTextField;
        target.DataValueField = dataValueField;
        target.DataBind();
    }
}

Now we can have an even simpler syntax for our binding operations:

public partial class _Default : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        if (!IsPostBack)
        {
            IEnumerable<BizObject> source = BizObjectFactory.GetAll();

            Binder.Bind(myCheckBox, source);
            Binder.Bind(myDropDown, source);
            Binder.Bind(myBulletedList, source);
            Binder.Bind(myListBox, source);
            Binder.Bind(myRadioButtonList, source);
        }
    }
}

Having this simple helper class will make life much easier (hint:  the same technique will work for windows projects).

Solution 3 (3.5 Framework):

If you are using the 3.5 Framework, we can simplify things even further by using extension methods:

public static class Binder
{
    public static void BindTo(this ListControl target, IEnumerable<BizObject> source)
    {
        Bind(target, source, "Value", "Key");
    }

    public static void BindTo<T>(this ListControl target, IEnumerable<T> source, String dataTextField, String dataValueField)
    {
        target.DataSource = source;
        target.DataTextField = dataTextField;
        target.DataValueField = dataValueField;
        target.DataBind();
    }
}

Now our consuming code will look like:

public partial class _Default : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        if (!IsPostBack)
        {
            IEnumerable<BizObject> source = BizObjectFactory.GetAll();

            myCheckBox.BindTo(source);
            myDropDown.BindTo(source);
            myBulletedList.BindTo(source);
            myListBox.BindTo(source);
            myRadioButtonList.BindTo(source);
        }
    }
}

The added bonus with using extension methods is that intellisense will now pick up on whether the Bind() method is available for each of our UI elements.

I hope you find this code consolidation pattern helpful.

Until next time,
Happy coding

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:
6 Months Free & No Setup Fees ASP.NET Hosting!
Become a Sponsor
 Comments
Team Foundation Server Hosting
 © 2012  contents copyright of their authors. Rest everything copyright Mindcracker. All rights reserved.