Home > Articles > Programming > Windows Programming

  • Print
  • + Share This
Like this article? We recommend

Like this article? We recommend

Binding to the DataList

Now that we have the Contact and Contacts classes and the DataList is properly defined, we can write the code that supports displaying and editing the values presented in the web page. Listing 3 provides the complete listing for the DataList sample application. (It's important to note that the web form designer code was concealed. Create an ASP.NET web application and then copy the code in Listing 3 to the web form.)

Listing 3—The Code-Behind Listing for the DataList Example

1: Imports Data
2:
3: Public Class WebForm1
4:   Inherits System.Web.UI.Page
5:  Protected WithEvents Button1 As _
6:   System.Web.UI.WebControls.Button
7:
8: [ Web Form Designer Generated Code ]
9:
10:   Private FContacts As Contacts
11:
12:   Private Sub Page_Load(ByVal sender _
13:    As System.Object, ByVal e As System.EventArgs) _
14:    Handles MyBase.Load
15:
16:    If (Session("Contacts") Is Nothing) Then
17:     FContacts = New Contacts()
18:     Session("Contacts") = FContacts
19:    Else
20:     FContacts = CType(Session("Contacts"), Contacts)
21:    End If
22:
23:    If (Not IsPostBack) Then
24:     BindData()
25:    End If
26:   End Sub
27:
28:   Private Function IsEmpty() As Boolean
29:    Return FContacts.Items.Count = 0
30:   End Function
31:
32:   Private Function GetLast() As Contact
33:    Return FContacts.Items(FContacts.Items.Count - 1)
34:   End Function
35:
36:   Private Function HasNewItem() As Boolean
37:    If (Not IsEmpty()) Then
38:    Return GetLast().FirstName = ""
39:    Else
40:     Return False
41:    End If
42:   End Function
43:
44:   Private Sub BindData()
45:    If (HasNewItem() = False) Then
46:     FContacts.Items.Add(New Contact())
47:    End If
48:
49:    DataList1.DataSource = FContacts.Items
50:    DataList1.DataBind()
51:   End Sub
52:
53:  Private Sub DataList1_EditCommand(ByVal source As Object, _
54:   ByVal e As System.Web.UI.WebControls.DataListCommandEventArgs) _
55:   Handles DataList1.EditCommand
56:
57:   DataList1.EditItemIndex = CInt(e.Item.ItemIndex)
58:   BindData()
59:  End Sub
60:
61:  Private Sub DataList1_UpdateCommand(ByVal source As Object, _
62:   ByVal e As System.Web.UI.WebControls.DataListCommandEventArgs) _
63:   Handles DataList1.UpdateCommand
64:
65:   Dim Contact As Contact = FContacts.Items(e.Item.ItemIndex)
66:
67:   Contact.FirstName = CType(e.Item.FindControl("TextBox1"), TextBox).Text
68:   Contact.LastName = CType(e.Item.FindControl("TextBox2"), TextBox).Text
69:   Contact.EMail = CType(e.Item.FindControl("TextBox3"), TextBox).Text
70:   Contact.URL = CType(e.Item.FindControl("TextBox4"), TextBox).Text
71:
72:   DataList1.EditItemIndex = -1
73:   BindData()
74:  End Sub
75:
76:  Private Sub DataList1_CancelCommand(ByVal source As Object, _
77:   ByVal e As System.Web.UI.WebControls.DataListCommandEventArgs) _
78:   Handles DataList1.CancelCommand
79:
80:   DataList1.EditItemIndex = -1
81:   BindData()
82:  End Sub
83:
84:  Private Sub DataList1_DeleteCommand(ByVal source As Object, _
85:   ByVal e As System.Web.UI.WebControls.DataListCommandEventArgs) _
86:   Handles DataList1.DeleteCommand
87:
88:   Try
89:    FContacts.Items.Remove(FContacts.Items(e.Item.ItemIndex))
90:   Finally
91:    DataList1.EditItemIndex = -1
92:    BindData()
93:   End Try
94:
95:  End Sub
96: End Class

The code designer was used to generate event methods for the form and the DataList. The Page_Load, DataList1_EditCommand, Datalist1_UpdateCommand, DataList1_CancelCommand, and DataList1_DeleteCommand event handlers were generated to support creating the Contacts object and responding to the four LinkButton commands: Edit, Update, Delete, and Cancel. When the page is loaded or refreshed, the Page_Load event handler code runs. When you click any of the LinkButton controls, the associated event handler code runs. For example, clicking the Edit LinkButton runs the DataList1_EditCommand.

Page Load Event

The Page_Load event code checks whether anything has been tucked into the Session cache. This technique can be used to determine whether the Contacts object has been created. If the object cannot be found in the Session cache, we need to create the Contacts object and put it in the cache. This occurs on lines 16–18 of Listing 3. If we have loaded the page at least once already, the Contacts object is retrieved from the cache rather than re-created. Keep in mind that we have to store the object somewhere; otherwise, the object state is not maintained between trips to and from the web server.

Line 23 checks whether this is a post back to the web server. If not, BindData is invoked to re-create the view of the DataList. BindData, on lines 44–51, was implemented to ensure that we always have a blank object to modify in our web page. On line 49 we set the Datalist1.DataSource property to the Items property of our Contacts object and invoke DataList1.DataBind to render the page.

Edit Command Event

When a user clicks the LinkButton that has the CommandName="edit" value, the DataList1_EditCommand event handler code runs. The EditCommand handler assigns the DataList1.EditItemIndex equal to the index of the selected item. The index is retrieved from a property of the DataListCommandEventArgs (see lines 53–54).

Changing the EditItemIndex to a positive integer places the DataList in edit mode. When we invoke BindData in edit mode, the DataList is rendered as described in the EditItemTemplate.

Cancel Command Event

The CancelCommand event handler is defined on lines 76–82. By setting the DataList1.EditItemIndex to -1 we effectively place the DataList back into browse mode. Binding the data renders the DataList as described in the ItemTemplate.

Delete Command Event

The DeleteCommand event handler is implemented to delete the currently selected item. Line 89 removes the Contact item from the list of contacts. Line 91 performs the same operation as the CancelCommand: the DataList is placed back into browse mode and we rebind the DataList control.

Update Command Event

The UpdateCommand is the most complex event handler. To update the state of the FContacts object, we need to read the value of the text boxes from the row we're editing in the DataList.

Updating occurs on lines 61–74. The first thing we do is get the index of the item we're currently editing and use that index to get a reference to the Contact item associated with this index. Then, on lines 67–70, we read each of the values from the TextBox controls, place the DataList in browse mode, and rebind.

Unfortunately, getting data out of the DataList is a little convoluted. Using line 67 as an example, the e.Item property is a DataListItem object. The DataListItem.FindControl method finds an identified control defined in that DataListItem—think row. (Keep in mind that you only defined a template; each DataListItem and the controls in that item were automatically created by the DataList.) The code dynamically casts the control to its real type, a TextBox, using the CType method, and the value is retrieved from the TextBox and assign to the Contact property.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020