Master Pages Control ID Naming in Content Pages Introduction

Master Pages  Control ID Naming in Content Pages IntroductionAll ASP.NET server controls include an ID property that uniquely identifies the control and is the means by which the control is programmatically accessed in the code-behind class. Similarly, the elements in an HTML document may include an id attribute that uniquely identifies the element; these id values are often used in client-side script to programmatically reference a particular HTML element. Given this, you may assume that when an ASP.NET server control is rendered into HTML, its ID value is used as the id value of the rendered HTML element. This is not necessarily the case because in certain circumstances a single control with a single ID value may appear multiple times in the rendered markup. Consider a GridView control that includes a TemplateField with a Label Web control with an ID value of ProductName. When the GridView is bound to its data source at runtime, this Label is repeated once for every GridView row. Each rendered Label needs a unique id value.

To handle such scenarios, ASP.NET allows certain controls to be denoted as naming containers. A naming container serves as a new ID namespace. Any server controls that appear within the naming container have their rendered id value prefixed with the ID of the naming container control. For example, the GridView and GridViewRow classes are both naming containers. Consequently, a Label control defined in a GridView TemplateField with ID ProductName is given a rendered id value of GridViewID_GridViewRowID_ProductName. Because GridViewRowID is unique for each GridView row, the resulting id values are unique.

Note: The INamingContainer interface is used to indicate that a particular ASP.NET server control should function as a naming container. The INamingContainer interface does not spell out any methods that the server control must implement; rather, it’s used as a marker. In generating the rendered markup, if a control implements this interface then the ASP.NET engine automatically prefixes its ID value to its descendents’ rendered id attribute values. This process is discussed in more detail in Step 2.

Naming containers not only change the rendered id attribute value, but also affect how the control may be programmatically referenced from the ASP.NET page’s code-behind class. The FindControl(“controlID”) method is commonly used to programmatically reference a Web control. However, FindControl does not penetrate through naming containers. Consequently, you cannot directly use the Page.FindControl method to reference controls within a GridView or other naming container.
As you may have surmised, master pages and ContentPlaceHolders are both implemented as naming containers. In this tutorial we examine how master pages affect HTML element id values and ways to programmatically reference Web controls within a content page using FindControl.

Website: download.microsoft.com | Filesize: 575kb
No of Page(s): 16
Click here to download Master Pages Control ID Naming in Content Pages Introduction.

Related Copyrighted Books
Professional ASP.NET 2.0 Design: CSS, Themes, and Master Pages (Programmer to Programmer)Professional ASP.NET 2.0 Design: CSS, Themes, and Master Pages (Programmer to Programmer)
Programming ASP.NET, 3rd EditionProgramming ASP.NET, 3rd Edition
Professional ASP.NET 2.0 Special EditionProfessional ASP.NET 2.0 Special Edition
ASP.NET Data Presentation Controls Essentials: Master the standard ASP.NET server controls for displaying and managing dataASP.NET Data Presentation Controls Essentials: Master the standard ASP.NET server controls for displaying and managing data
Pro ASP.NET 3.5 in C# 2008: Includes Silverlight 2, Third EditionPro ASP.NET 3.5 in C# 2008: Includes Silverlight 2, Third Edition

Related Tutorial

Tags: , ,

Comments

Comments are closed.