Home > Articles > Web Services > XML

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

An XML Node Representing a Simple Macro Language

Before you start defining a custom configuration section handler, you should know how what the XML you want to handle will look like. For completeness, we'll define some XML, too.


If you're building a section handler for predefined XML, you can skip ahead to the section "Implementing the Section Handler."

Suppose you elected to permit controlling your application from its external app.config or web.config with a node that represents a user-defined macro language. Such a technique would permit automatically performing tasks at startup and might be a good choice for batch processing or for completing required, configurable startup tasks.

To begin prototyping a startup macro language solution, we'll need to perform these general steps, described in the subsections that follow:

  1. Add a .config file to your solution.

  2. Add a <configSections> node that points the framework at your custom node.

  3. Define the custom XML node.

If you're very familiar with any of these aspects of Visual Studio .NET and .NET programming, feel free to skip that particular section.

Adding a .config File to Your Solution

Visual Studio .NET supports templates. A template is little more than a preexisting wizard and some stubbed-out source files with replaceable parameters. You select an icon representing the template, and the wizard fills in the blanks using the Visual Studio .NET automation model.

Visual Basic traditionally has a lower barrier to entry than languages such as C#, so Visual Basic .NET programmers had the Application Configuration template in version 1 of .NET. Now C# programmers have it, too.

If you want the startup macro to run in a web application, use the web.config file. For non-Internet solutions, add an application configuration (app.config) file from the Add New Item dialog box (see Figure 1).

Figure 1Figure 1 The Application Configuration template adds an app.config file to your project.

After you add an app.config file using Project, Add New Item, the compiler will copy the .config file to your solution's bin folder, renaming the file application_name.ext.config. For example, if your solution is called ConfigSectionHandler.exe, after you compile your solution the compiler will copy the app.config file to the bin folder, renaming the file ConfigSectionHandler.exe.config.

Defining the <configSections> Node

The next step is to provide an indicator that tells the framework that you have custom configuration sections. .NET already knows to look for a <configSections> node, in which you introduce custom sections. Listing 1 shows the first part of the app.config file with the <configSections> node in bold.

Listing 1 The <configSections> node for our custom handler.

<?xml version="1.0" encoding="utf-8" ?>
 <section name="startupMacro" type="ConfigSectionHandler.MacroSectionHandler, ConfigSectionHandler" />

Let's break it down briefly:

  • The <section> tag indicates that we're introducing a new section.

  • The name attribute indicates what that section's node tag is called. The <configSections> in Listing 1 indicates that we should have a node named <startupMacro> later in this XML file.

  • The type attribute describes the namespace and class, delimited with a comma and the assembly name of the class. Assembly names, namespaces, and class names are enough to use Reflection to dynamically find and load a .NET assembly, which is precisely what the framework will be doing here.

Defining the Custom XML Node

Next, we need to define the <startupMacro> node. Because the macro language is our invention, we can use any valid XML to represent our macro language. However, to demonstrate reasonable plausibility, I made the example section functional. Listing 2 shows the completed app.config XML file with the <startupMacro> tag.

Listing 2 The completed App.config file.

<?xml version="1.0" encoding="utf-8" ?>
 <section name="startupMacro" type="ConfigSectionHandler.MacroSectionHandler, ConfigSectionHandler" />

 <startupMacro mode="On">
  <command name="App_About">
  <delay value="5" />
  <command name="App_Quit">
  <delay value="10" />


XML stands for Extensible Markup Language. Extensibility means that we can define our own tags, which is precisely what happens in Listings 1 and 2. And, because we can define our own tags, we can nest them and add any attributes we'd like:

  • The <startupMacro> tag has a mode attribute, which I use to toggle the macro between on and off states.

  • I also defined two <command> child nodes—of course, we can define as many as we'd like—with a name attribute for each, and a nested <delay> node. In this example, the order implies the order of execution. The name attribute is associated with a behavior in my application—the Command behavior pattern would work well here—and the delay is in seconds. delay tells the application how long it should wait before executing that command.


For more on behavior patterns, see Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley, 1994, ISBN 0201633612) by Erich Gamma et al.

At this point, we need to implement an IConfigSectionHandler and support our macro behaviors.

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