Order of Precedence for Form Definition Properties

  • Article

Order of Precedence for Form Definition Properties

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

To prevent conflicting values, a specific order of preference is used to determine which property takes precedence when the form registration is read.

A non-wildcard value has the highest precedence, a wildcard value has middle precedence, and a null value has lowest precedence. Attributes must match exactly, except for browser capability.

The registry uses the following order of precedence:

  1. HTTP request
  2. URL action (cmd)
  3. Message-State
  4. Content-State
  5. Browser capability (browser type and version)
  6. Version
  7. Platform
  8. MajorVer
  9. MinorVer
  10. Language

For the version properties, the precedence order (highest to lowest) is =, <=, >=, <, >, *, and then null.

Browser capability comparisons are as follows:

= equals

<= less than or equal to

>= greater than or equal to

< less than

> greater than

Send us your feedback about the Microsoft Exchange Server 2003 SDK.

Build: June 2007 (2007.618.1)

© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.