Home > Articles > Programming > ASP .NET

ASP.NET Extensibility With XML

Explore how XML is integrated with the configuration of Windows Forms and Web Forms applications using the ASP.NET web.config files.
This chapter is from the book

This chapter is from the book

Throughout this book, it's been shown that .NET incorporates XML into key areas of the .NET Framework, as well as into technologies, such as ADO.NET. This chapter discusses how XML is integrated with the configuration of Windows Forms and Web Forms applications.

A Word on the Metabase

The process for configuring the operating system and applications that run on it has evolved since MS-DOS' inception. To configure MS-DOS, AUTOEXEC.BAT and CONFIG.SYS files were used, and applications running on top of the operating system used their own proprietary configuration files. Back in the days of Windows 3.1, people were introduced to .INI files that stored configuration information. A set of simple APIs were included to work with .INI files in a standard fashion (remember GetProfileString and GetProfileSection?). A simple tool called sysedit provided easy access to edit the SYSTEM.INI, WIN.INI, CONFIG.SYS, and AUTOEXEC.BAT files by simply loading all of them into a Multiple Document Interface (MDI) window.

When Windows NT 3.5 was released, everyone became more familiar with the registry. It wasn't until Windows 95 was released, however, that people saw the true ability to control the operating system, expecially with the release of PowerToys, an application designed to customize the Windows 95 UI. The registry allowed for easier development of hierarchical structures that could contain both text and binary data in several formats. The registry became favored over .INI files.

The release of Windows NT 4.0 increased the use of the registry. But when the Option Pack for Windows NT 4.0 was released (including IIS 3.0), developers quickly became intimately familiar with tweaking the registry to manipulate IIS for capabilities such as ADO connection pooling and connection timeouts. Microsoft's integration of some of these registry settings into the Microsoft Mangement Console (MMC) snap-in eased the developer's research time, but it was soon realized that using the registry for IIS management was not an optimal solution because of speed and complexity issues.

The solution to using the registry is provided by the metabase. The metabase is a binary file that provides hierarchical configuration information for Internet Information Services (IIS). It is located at %windir%\system32\inetsrv\ MetaBase.bin. Several utilities are available for working with the metabase, including the Internet Services Manager MMC snap-in.

In ASP.NET, configuration information is stored in XML configuration files. These XML files can be modified while the server is running, and changes take effect without rebooting the web server. If you have ever had to go back to work at 3 a.m. to reboot the web server, you'll appreciate this new feature. The managed code configuration system reads the values and applies them without restarting the server. The exception to this case is the processModel section—it's read directly by aspnet_isapi.dll. Changes do not take effect in this section until IIS is restarted.

Several configuration files are available that you can use with the .NET Framework: security configuration files, the machine configuration file (machine.config), and application configuration files.

Security Configuration Files

Security configuration files manage the permissions associated with a policy level and the code group hierarchy. These settings need to be modified using only the .NET Configuration MMC snap-in (mscorcfg.msc) or by using the Code Access Security Policy tool (caspol.exe).

machine.config

The machine configuration file, machine.config, specifies machine-wide settings. It contains settings for machine-wide ASP.NET, as well as assembly binding and built-in remoting channels. You can also specify custom settings in its appSettings section (described in the section, "Walk-Through of web.config's Hierarchical Structure"). It's recommended that application- specific settings be placed in their associated application configuration files unless they pertain to all applications on the machine.

Application Configuration Files

A benefit to using configuration files at the application level is that each application can configure the environment for its own use. For example, one of the settings available in a configuration file is the requiredRuntime setting in the startup section. It defines what version of the run-time to use. For machines with multiple versions of the common language run-time installed, this key can be used to manage on which version the application depends.

Two types of application configuration files exist: executable-hosted configuration files and web application configuration files (web.config).

Executable Configuration Files

Executable configuration files manage the configuration settings for the executable environment. The application configuration file is not compiled into the executable file as a resource file is. Rather, the configuration file is external to the application and uses the same name as the application with a .config extension. For example, an application named WindowsApplication.exe would have a single configuration file in its bin directory when it's compiled as WindowsApplication.exe.config. Unless this setting matches the executable name, the configuration file is not found.

web.config

When the application to be configured is a web application, the configuration file used is called web.config. When you create a new ASP.NET web application project in Visual Studio .NET, a web.config file is included in the list of files that is automatically generated.

Not only can the application's virtual root have a web.config file, but each subdirectory in the virtual directory can also have its own web.config file. Each web.config file applies its settings to its own virtual directory and its virtual subdirectories. If a conflict in settings occurs between a directory and a subdirectory, the settings in the subdirectory take precedence over the parent directory's settings. For example, look at the virtual directory structure in Figure 7.1.

Configuration Files Are Secured in ASP.NET

ASP.NET configuration files are secured and are not viewable through a browser: An attempt to access the web.config file causes an HTTP error, 403 (Forbidden).

Figure 7.1 Each subdirectory in the virtual directory might have its own web.config file.

The Public directory doesn't have its own web.config file: Settings are inherited from the parent Application directory.

The Secure directory, which represents the set of web pages that require authentication, uses its own web.config file separately from the parent Application directory. In this model, a conflicting setting in the Secure directory's web.config file would be used. Any settings not specifically overridden in the child directory would be inherited from the parent directory. This enables the developer to require a different authentication model for each subdirectory if desired, or to use the settings for the parent directory. This also prevents the user from duplicating custom application settings for each virtual subdirectory.

Take a look at the components of the web.config file and see what configuration options are available.

Configuration Settings Are URL Specific

Settings are inherited by subdirectories according to the URL, not the physical disk path.

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