Home > Articles > Programming > C#

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

Like this article? We recommend

Building Web Forms with User Controls

With user controls, you can build web pages quickly, leaving you time to concentrate on other content that's unique to a specific page or that changes dynamically over time. This example demonstrates how to create a web page with user controls.

The first page we'll work with is the home page:

  1. There's probably a web page in your project named WebForm1.aspx, which is the default name assigned when you run the wizard. Change the filename to Default.aspx and open the file in the designer.

  2. Next, you'll need to do some initial layout of the page. Select the Document element from the drop-down list in the Object Inspector and change the PageLayout property from GridLayout to FlowLayout.

  3. Add a table to Default.aspx with one row and two columns. Set the width to 100% and change the border width to 0. After creating the table, click the left cell of the new table, change its width property to 125, and change its valign property to "top" in the Object Inspector. Now the layout and structure of the page is set.

After initial layout, you can add controls to the web page. One thing that's a real bother with C#Builder is that you can't do drag-and-drop with user controls. Once the control is on the page, you can select it and delete it, but the fact that Borland left out such an obvious necessity on a GUI designer is difficult to believe. Anyway, a workaround is available, and fortunately, C#Builder has a nice HTML editor to work with. Switch to the HTML page of Default.aspx to continue designing with user controls.

When you put a user control on a web page, you need to tell ASP.NET how to identify and associate a page element that represents the control with the control itself. To accomplish this, another directive called Register is placed on each web page where the control is added. Each web page in this example needs three Register directives, as shown in Listing 2.

Listing 2 Register Directives

<%@ Register
   Src="HeaderControl.ascx" %>
<%@ Register
   Src="FooterControl.ascx" %>
<%@ Register
   Src="MenuControl.ascx" %>

Each Register directive in Listing 2 contains the same three attributes:

  • The TagPrefix attribute identifies the namespace (think XML) to which elements of this control are assigned. This is similar to the asp: prefix on ASP.NET web controls that ship with .NET, which keeps the names of controls in different libraries from clashing. For instance, I could add a control to my library named Button; it wouldn't conflict with asp:Button because it would be referred to on the page as InformIT:Button as defined by a Register directive.

  • The TagName attribute identifies the name of the control as it will be used on the web page. You can essentially give the TagPrefix and TagName attributes any value you want, as long as they didn't conflict with the naming conventions of other controls on the web page.

  • The Src attribute specifies the filename of a user control and is the mechanism that associates the actual control with how it's identified on the web page.

Once Register directives have been added, you can insert elements in the HTML where you want each control to appear. Here's the syntax for coding a user control:

<InformIT:Header runat="server" />

To save yourself some typing, you can specify the user control as shown in Listing 3. However, as soon as you click the Save button or move to the Design window, C#Builder transforms your HTML into the format shown below:

<informit:header id=userControl1 runat="server">

Of course, the code above still works, or else C#Builder wouldn't have changed it. Feel free to change the value of the id attribute to something more meaningful for this control—especially if you want to access the control from code. If you do reference this control from code, be sure to add a variable of the proper type with an identifier that matches the id attribute. Controls are objects, just like any other object, and you can add any event, method, or property you need to make the control work the way you want. Public fields and properties can be set as attributes in HTML or via entries in the Object Inspector. For example, the declaration below references the HeaderControl control shown above:

HeaderControl userControl1;

The type here is the same type declared in the code-behind of the HeaderControl user control. Notice that the identifier userControl1 matches the id attribute of the InformIT:Header control element in the HTML of Default.aspx. The identifier is not very intuitive and should be changed in both the HTML and code-behind of Default.aspx. Because program access (events, methods, and properties) to user controls is the subject of another article, I'll leave that part of the discussion and move forward with showing you how to add user controls to a web page.

Now that you know how to add a control, the next step is to add each of the user controls to the web page. HeaderControl goes just before the table, FooterControl goes at the bottom of the table, and MenuControl goes in the first column. Listing 3 contains the HTML, showing where each of the controls goes.

Listing 3 Web Page HTML with User Controls Added

<%@ Page language="c#"
  Inherits="CraftingUserControls.WebForm1" %>
<%@ Register
   Src="HeaderControl.ascx" %>
<%@ Register
   Src="FooterControl.ascx" %>
<%@ Register
   Src="MenuControl.ascx" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

  <meta name="GENERATOR" content="Borland ASP.NET Designer for c# Package Library 7.1">

 <body ms_positioning="FlowLayout">
 <form runat="server">
  <informit:header id=userControl1 runat="server">
  <table cellspacing=0 cellpadding=1 width="100%" border=0>
     <td valign=top width=125>
      <informit:menu id=userControl2 runat="server">
  <informit:footer id=userControl3 runat="server">

Each control added to the HTML appears in bold in Listing 3. Each control element will be replaced with the contents of the control when the page is rendered. The only step left for this page is content, which is easier to add via the visual designer. Figure 6 shows how this page looks in the visual designer with content added.

Figure 6Figure 6 The Visual Designer displays user controls as gray boxes with identifiers. You can't see how the page looks, but you can see where the controls are located.

The visual designer in Figure 6 shows what a Web page looks like with controls and content added. The controls are gray boxes and simply help show where they should reside, giving you an idea of where they will appear when the page is rendered. When launched, the web page will actually look like Figure 7.

Figure 7Figure 7 When the page runs, all controls will be rendered as part of the original web page. The page is responsive and the user experience hasn't changed at all.

As an exercise, add a new web form to this project and name it About.aspx. Add the tables and controls as described for Default.aspx. Add any content that you think an About page should have. When running the application, you can switch between pages via the menu, and both pages have the same header, menu, and footer elements.

To see the real value of user controls, change the contents on one of the controls; for example, add a copyright notice to the footer. Notice that the change appears on both pages. When considering the impact of that one change across a large site with hundreds of pages, you can easily see the huge boost in productivity that user controls deliver.

  • + 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.


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.


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.


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.


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


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


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.


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.


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