Wednesday, August 1, 2007

Why is my custom policy file generating strange errors?

If you are using a custom policy file, you may encounter the following errors when compiling your solution:

· Stage should contain at least components

· Identifier expected

The first problem occurs when the number of components required per stage is less than the number of components in the stage. The second problem occurs when the execution mode value defined for some stage in the policy file is None; only FirstMatch and All are allowed.

To fix these errors, you must edit your custom policy file to include the proper values. For example, in the configuration below the number of components per stage must be adjusted:

<?xml version="1.0" encoding="utf-8"?>

<document xsd="" xsi="" categoryid="" friendlyname="">

<stages>

<stage name="Decode" minoccurs="5" maxoccurs="10" execmethod="All"></stage>

</stages>

</document>

The Stage element attribute minOccurs must be changed to "1" as shown below.

<?xml version="1.0" encoding="utf-8"?>

<document xsd="" xsi="" categoryid="" friendlyname="">

<stages>

<stage name="Decode" minoccurs="1" maxoccurs="10" execmethod="All"></stage>

</stages>

</document>



Source: Microsoft

No comments: