Skip to content

Latest commit

 

History

History
75 lines (54 loc) · 5.89 KB

validationsection-class.md

File metadata and controls

75 lines (54 loc) · 5.89 KB
Raw
title description ms.date ms.assetid
ValidationSection Class
This article shares the syntax, methods, and properties of the ValidationSection Class, which enables or disables validation checks on configuration files.
10/07/2016
da81aca7-b37a-42a3-8b32-b1ae2a4966e2

ValidationSection Class

Enables or disables validation checks on configuration files.

Syntax

class ValidationSection : ConfigurationSection

Methods

The following table lists the methods exposed by the ValidationSection class.

Name Description
GetAllowDefinition (Inherited from ConfigurationSection.)
GetAllowLocation (Inherited from ConfigurationSection.)
RevertToParent (Inherited from ConfigurationSection.)
SetAllowDefinition (Inherited from ConfigurationSection.)
SetAllowLocation (Inherited from ConfigurationSection.)

Properties

The following table lists the properties exposed by the ValidationSection class.

Name Description
Location (Inherited from ConfigurationSection.) A key property.
Path (Inherited from ConfigurationSection.) A key property.
SectionInformation (Inherited from ConfigurationSection.)
ValidateIntegratedModeConfiguration A read/write boolean value. true if IIS generates a migration error message when it detects that an ASP.NET 1.0 Web application should be modified to run in Integrated mode; otherwise, false. The default value is true. For more information about this property, see the Remarks section.

Subclasses

This class contains no subclasses.

Remarks

IIS generates a migration error message if the ValidateIntegratedModeConfiguration property is enabled and one of the following is true:

  • Your application defines an <httpModules> section in its Web.config file.

    In [!INCLUDEiisver] Integrated mode, [!INCLUDEvstecasp] modules are specified with native modules in a unified <modules> section under <system.webServer>.

  • Your application defines an <httpHandlers> section in its Web.config file.

    In [!INCLUDEiisver] Integrated mode, the [!INCLUDEvstecasp] handler mappings are specified in a unified <handlers> section inside <system.webServer>. The <handlers> section replaces both the [!INCLUDEvstecasp] <httpHandlers> and IIS script-processor-mapping configurations, which were both required to set up a ASP.NET 1.0 handler mapping.

  • Your application's Web.config file specifies <identity impersonate="true" />.

    In [!INCLUDEiisver] Integrated mode, client impersonation is not available in some early request processing stages. Therefore, IIS will generate the migration error message. If your [!INCLUDEvstecasp] Web application impersonates client credentials (most common with intranet scenarios), you may want to set the ValidateIntegratedModeConfiguration property to false.

    If you migrate your configuration manually, or you do not migrate your configuration but you want IIS to remain in Integrated mode (which you should avoid), you can disable migration error messages by setting the ValidateIntegratedModeConfiguration property to false.

Note

Because IIS will no longer provide warnings for unsupported configurations when ValidateIntegratedModeConfiguration is false, ensure that your application works correctly in Integrated mode before you make this setting.

Inheritance Hierarchy

ConfigurationSection

ValidationSection

Requirements

Type Description
Client - [!INCLUDEiis70] on [!INCLUDEwinvista]
- [!INCLUDEiis75] on [!INCLUDEwin7]
- [!INCLUDEiis80] on [!INCLUDEwin8]
- [!INCLUDEiis100] on [!INCLUDEwin10]
Server - [!INCLUDEiis70] on [!INCLUDEwinsrv2008]
- [!INCLUDEiis75] on [!INCLUDEwinsrv2008r2]
- [!INCLUDEiis80] on [!INCLUDEwinsrv2012]
- [!INCLUDEiis85] on [!INCLUDEwinsrv2012r2]
- [!INCLUDEiis100] on [!INCLUDEwinsrv2016]
Product - [!INCLUDEiis70], [!INCLUDEiis75], [!INCLUDEiis80], [!INCLUDEiis85], [!INCLUDEiis100]
MOF file WebAdministration.mof

See Also

ConfigurationSection Class