<?xml version='1.0' encoding='utf-8'?>
<!-- Copyright (c) .NET Foundation and contributors. All rights reserved. Licensed under the Microsoft Reciprocal License. See LICENSE.TXT file in the project root for full license information. -->


<Messages Namespace="Microsoft.Tools.WindowsInstallerXml" Resources="Data.Messages" xmlns="http://schemas.microsoft.com/genmsgs/2004/07/messages">
    <Class Name="WixErrors" ContainerName="WixErrorEventArgs" BaseContainerName="MessageEventArgs" Level="Error">
        <Message Id="UnexpectedException" Number="1" SourceLineNumbers="no">
            <Instance>
                {0}&#13;&#10;&#13;&#10;Exception Type: {1}&#13;&#10;&#13;&#10;Stack Trace:&#13;&#10;{2}
                <Parameter Type="System.String" Name="message" />
                <Parameter Type="System.String" Name="type" />
                <Parameter Type="System.String" Name="stackTrace" />
            </Instance>
        </Message>
        <Message Id="UnexpectedAttribute" Number="4">
            <Instance>
                The {0} element contains an unexpected attribute '{1}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="UnexpectedElement" Number="5">
            <Instance>
                The {0} element contains an unexpected child element '{1}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="childElementName" />
            </Instance>
        </Message>
        <Message Id="IllegalEmptyAttributeValue" Number="6">
            <Instance>
                The {0}/@{1} attribute's value cannot be an empty string. If a value is not required, simply remove the entire attribute.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value cannot be an empty string.  To use the default value "{2}", simply remove the entire attribute.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="defaultValue" />
            </Instance>
        </Message>
        <Message Id="InsufficientVersion" Number="7">
            <Instance>
                The current version of the toolset is {0}, but version {1} is required.
                <Parameter Type="System.Version" Name="currentVersion" />
                <Parameter Type="System.Version" Name="requiredVersion" />
            </Instance>
            <Instance>
                The current version of the extension '{2}' is {0}, but version {1} is required.
                <Parameter Type="System.Version" Name="currentVersion" />
                <Parameter Type="System.Version" Name="requiredVersion" />
                <Parameter Type="System.String" Name="extension" />
            </Instance>
        </Message>
        <Message Id="IllegalIntegerValue" Number="8">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a legal integer value.  Legal integer values are from -2,147,483,648 to 2,147,483,647.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="IllegalGuidValue" Number="9">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a legal guid value.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="ExpectedAttribute" Number="10">
            <Instance>
                The {0}/@{1} attribute was not found; it is required.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
            <Instance>
                The {0} element must have a value for exactly one of the {1} or {2} attributes.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attribute1Name" />
                <Parameter Type="System.String" Name="attribute2Name" />
                <Parameter Type="System.Boolean" Name="eitherOr" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute was not found; it is required when attribute {2} is specified.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute was not found; it is required when attribute {2} has a value of '{3}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName" />
                <Parameter Type="System.String" Name="otherAttributeValue" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute was not found; it is required unless the attribute {2} has a value of '{3}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName" />
                <Parameter Type="System.String" Name="otherAttributeValue" />
                <Parameter Type="System.Boolean" Name="otherAttributeValueUnless" />
            </Instance>
        </Message>
        <Message Id="SecurePropertyNotUppercase" Number="11">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', cannot contain lowercase characters.  Since this is a secure property, it must also be a public property.  This means the Property/@Id value must be completely uppercase.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="propertyId" />
            </Instance>
        </Message>
        <Message Id="SearchPropertyNotUppercase" Number="12">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', cannot contain lowercase characters.  Since this is a search property, it must also be a public property.  This means the Property/@Id value must be completely uppercase.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="StreamNameTooLong" Number="13">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is {3} characters long.  This is too long because it will be used to create a stream name.  It cannot be more than than {4} characters long.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.Int32" Name="length" />
                <Parameter Type="System.Int32" Name="maximumLength" />
            </Instance>
            <Instance>
                The binary value in table '{0}' will be stored with a stream name, '{1}', that is {2} characters long.  This is too long because the maximum allowed length for a stream name is 62 characters long.  Since the stream name is created by concatenating the table name and values of the primary key for a row (delimited by periods), this error can be resolved by shortening a value that is part of the primary key.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="streamName" />
                <Parameter Type="System.Int32" Name="streamLength" />
            </Instance>
        </Message>
        <Message Id="IllegalIdentifier" Number="14">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a legal identifier.  Identifiers may contain ASCII characters A-Z, a-z, digits, underscores (_), or periods (.).  Every identifier must begin with either a letter or an underscore.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value is not a legal identifier.  Identifiers may contain ASCII characters A-Z, a-z, digits, underscores (_), or periods (.).  Every identifier must begin with either a letter or an underscore.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.Int32" Name="disambiguator" />
            </Instance>
            <Instance>
                The {0} element's value, '{1}', is not a legal identifier.  Identifiers may contain ASCII characters A-Z, a-z, digits, underscores (_), or periods (.).  Every identifier must begin with either a letter or an underscore.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="IllegalYesNoValue" Number="15">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a legal yes/no value.  The only legal values are 'no' and 'yes'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="CabCreationFailed" Number="16" SourceLineNumbers="no">
            <Instance>
                Failed to create cab '{0}' while compressing file '{1}' with error 0x{2:X8}.
                <Parameter Type="System.String" Name="cabName" />
                <Parameter Type="System.String" Name="fileName" />
                <Parameter Type="System.Int32" Name="error" />
            </Instance>
            <Instance>
                Failed to create cab '{0}' with error 0x{1:X8}.
                <Parameter Type="System.String" Name="cabName" />
                <Parameter Type="System.Int32" Name="error" />
            </Instance>
        </Message>
        <Message Id="CabExtractionFailed" Number="17" SourceLineNumbers="no">
            <Instance>
                Failed to extract cab '{0}' to directory '{1}'.  This is most likely due to a lack of available disk space on the destination drive.
                <Parameter Type="System.String" Name="cabName" />
                <Parameter Type="System.String" Name="directoryName" />
            </Instance>
            <Instance>
                Failed to extract cab '{0}' from merge module '{1}' to directory '{2}'.  This is most likely due to a lack of available disk space on the destination drive.
                <Parameter Type="System.String" Name="cabName" />
                <Parameter Type="System.String" Name="mergeModulePath" />
                <Parameter Type="System.String" Name="directoryName" />
            </Instance>
        </Message>
        <Message Id="AppIdIncompatibleAdvertiseState" Number="18">
            <Instance>
                The {0}/@(1) attribute's value, '{2}' does not match the advertise state on its parent element: '{3}'.  (Note: AppIds nested under Fragment, Module, or Product elements must be advertised.)
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="parentValue" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeWhenAdvertised" Number="19">
            <Instance>
                The {0}/@{1} attribute cannot be specified because the element is advertised.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="ConditionExpected" Number="20">
            <Instance>
                The {0} element's inner text cannot be an empty string or completely whitespace.  If you don't want a condition, then simply remove the entire {0} element.
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeValue" Number="21">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="legalValue1" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', or '{4}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="legalValue1" />
                <Parameter Type="System.String" Name="legalValue2" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', or '{5}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="legalValue1" />
                <Parameter Type="System.String" Name="legalValue2" />
                <Parameter Type="System.String" Name="legalValue3" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', or '{6}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="legalValue1" />
                <Parameter Type="System.String" Name="legalValue2" />
                <Parameter Type="System.String" Name="legalValue3" />
                <Parameter Type="System.String" Name="legalValue4" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', '{6}', or '{7}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="legalValue1" />
                <Parameter Type="System.String" Name="legalValue2" />
                <Parameter Type="System.String" Name="legalValue3" />
                <Parameter Type="System.String" Name="legalValue4" />
                <Parameter Type="System.String" Name="legalValue5" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', '{6}', '{7}', or '{8}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="legalValue1" />
                <Parameter Type="System.String" Name="legalValue2" />
                <Parameter Type="System.String" Name="legalValue3" />
                <Parameter Type="System.String" Name="legalValue4" />
                <Parameter Type="System.String" Name="legalValue5" />
                <Parameter Type="System.String" Name="legalValue6" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', '{6}', '{7}', '{8}', or '{9}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="legalValue1" />
                <Parameter Type="System.String" Name="legalValue2" />
                <Parameter Type="System.String" Name="legalValue3" />
                <Parameter Type="System.String" Name="legalValue4" />
                <Parameter Type="System.String" Name="legalValue5" />
                <Parameter Type="System.String" Name="legalValue6" />
                <Parameter Type="System.String" Name="legalValue7" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', '{6}', '{7}', '{8}', '{9}', or '{10}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="legalValue1" />
                <Parameter Type="System.String" Name="legalValue2" />
                <Parameter Type="System.String" Name="legalValue3" />
                <Parameter Type="System.String" Name="legalValue4" />
                <Parameter Type="System.String" Name="legalValue5" />
                <Parameter Type="System.String" Name="legalValue6" />
                <Parameter Type="System.String" Name="legalValue7" />
                <Parameter Type="System.String" Name="legalValue8" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', '{6}', '{7}', '{8}', '{9}', '{10}', '{11}', '{12}', '{13}', '{14}', '{15}', '{16}', '{17}', '{18}', '{19}', '{20}', '{21}', '{22}', '{23}', '{24}', '{25}', '{26}', '{27}', or '{28}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="legalValue1" />
                <Parameter Type="System.String" Name="legalValue2" />
                <Parameter Type="System.String" Name="legalValue3" />
                <Parameter Type="System.String" Name="legalValue4" />
                <Parameter Type="System.String" Name="legalValue5" />
                <Parameter Type="System.String" Name="legalValue6" />
                <Parameter Type="System.String" Name="legalValue7" />
                <Parameter Type="System.String" Name="legalValue8" />
                <Parameter Type="System.String" Name="legalValue9" />
                <Parameter Type="System.String" Name="legalValue10" />
                <Parameter Type="System.String" Name="legalValue11" />
                <Parameter Type="System.String" Name="legalValue12" />
                <Parameter Type="System.String" Name="legalValue13" />
                <Parameter Type="System.String" Name="legalValue14" />
                <Parameter Type="System.String" Name="legalValue15" />
                <Parameter Type="System.String" Name="legalValue16" />
                <Parameter Type="System.String" Name="legalValue17" />
                <Parameter Type="System.String" Name="legalValue18" />
                <Parameter Type="System.String" Name="legalValue19" />
                <Parameter Type="System.String" Name="legalValue20" />
                <Parameter Type="System.String" Name="legalValue21" />
                <Parameter Type="System.String" Name="legalValue22" />
                <Parameter Type="System.String" Name="legalValue23" />
                <Parameter Type="System.String" Name="legalValue24" />
                <Parameter Type="System.String" Name="legalValue25" />
                <Parameter Type="System.String" Name="legalValue26" />
            </Instance>
        </Message>
        <Message Id="CustomActionMultipleSources" Number="22">
            <Instance>
                The {0}/@{1} attribute cannot coexist with a previously specified attribute on this element.  The {0} element may only have one of the following source attributes specified at a time: {2}, {3}, {4}, {5}, or {6}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
                <Parameter Type="System.String" Name="attributeName3" />
                <Parameter Type="System.String" Name="attributeName4" />
                <Parameter Type="System.String" Name="attributeName5" />
            </Instance>
        </Message>
        <Message Id="CustomActionMultipleTargets" Number="23">
            <Instance>
                The {0}/@{1} attribute cannot coexist with a previously specified attribute on this element.  The {0} element may only have one of the following target attributes specified at a time: {2}, {3}, {4}, {5}, {6}, {7}, or {8}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
                <Parameter Type="System.String" Name="attributeName3" />
                <Parameter Type="System.String" Name="attributeName4" />
                <Parameter Type="System.String" Name="attributeName5" />
                <Parameter Type="System.String" Name="attributeName6" />
                <Parameter Type="System.String" Name="attributeName7" />
            </Instance>
        </Message>
        <Message Id="CustomActionIllegalInnerText" Number="24">
            <Instance>
                The {0} element contains illegal inner text: '{1}'.  It may not contain inner text unless the {2} attribute is specified.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="innerText" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="DirectoryRootWithoutName" Number="25">
            <Instance>
                The {0} element requires the {1} attribute because there is no parent {0} element.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="IllegalShortFilename" Number="26">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a valid 8.3-compliant name.  Legal names contain no more than 8 non-period characters followed by an optional period and extension of no more than 3 non-period characters.  Any character except for the follow may be used: \ ? | &gt; &lt; : / * " + , ; = [ ] (space).
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="IllegalLongFilename" Number="27">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a valid long name because it contains illegal characters.  Legal long names contain no more than 260 characters and must contain at least one non-period character.  Any character except for the follow may be used: \ ? | &gt; &lt; : / * ".
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="TableNameTooLong" Number="28">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is too long for a table name.  It cannot be more than than 31 characters long.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="FeatureConfigurableDirectoryNotUppercase" Number="29">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', contains lowercase characters.  Since this directory is user-configurable, it needs to be a public property.  This means the value must be completely uppercase.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="FeatureCannotFavorAndDisallowAdvertise" Number="30">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', cannot coexist with the {3} attribute's value of '{4}'.  These options would ask the installer to disallow the advertised state for this feature while at the same time favoring it.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="otherAttributeName" />
                <Parameter Type="System.String" Name="otherValue" />
            </Instance>
        </Message>
        <Message Id="FeatureCannotFollowParentAndFavorLocalOrSource" Number="31">
            <Instance>
                The {0}/@{1} attribute cannot be specified if the {2} attribute's value is '{3}'.  These options would ask the installer to force this feature to follow the parent installation state and simultaneously favor a particular installation state just for this feature.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName" />
                <Parameter Type="System.String" Name="otherValue" />
            </Instance>
        </Message>
        <Message Id="MediaEmbeddedCabinetNameTooLong" Number="32">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is {3} characters long.  The name is too long for an embedded cabinet.  It cannot be more than than 62 characters long.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.Int32" Name="length" />
            </Instance>
        </Message>
        <Message Id="RegistrySubElementCannotBeRemoved" Number="33">
            <Instance>
                The {0}/{1} element cannot be specified if the {2} attribute's value is '{3}' or '{4}'.
                <Parameter Type="System.String" Name="registryElementName" />
                <Parameter Type="System.String" Name="registryValueElementName" />
                <Parameter Type="System.String" Name="actionAttributeName" />
                <Parameter Type="System.String" Name="removeValue" />
                <Parameter Type="System.String" Name="removeKeyOnInstallValue" />
            </Instance>
        </Message>
        <Message Id="RegistryMultipleValuesWithoutMultiString" Number="34">
            <Instance>
                The {0}/@{1} attribute and a {0}/{2} element cannot both be specified.  Only one may be specified if the {3} attribute's value is not 'multiString'.
                <Parameter Type="System.String" Name="registryElementName" />
                <Parameter Type="System.String" Name="valueAttributeName" />
                <Parameter Type="System.String" Name="registryValueElementName" />
                <Parameter Type="System.String" Name="typeAttributeName" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeWithOtherAttribute" Number="35">
            <Instance>
                The {0}/@{1} attribute cannot be specified when attribute {2} is present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute cannot be specified when attribute {2} is present with value '{3}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName" />
                <Parameter Type="System.String" Name="otherAttributeValue" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeWithOtherAttributes" Number="36">
            <Instance>
                The {0}/@{1} attribute cannot be specified when attribute {2} or {3} is also present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName1" />
                <Parameter Type="System.String" Name="otherAttributeName2" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute cannot be specified when attribute {2}, {3}, or {4} is also present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName1" />
                <Parameter Type="System.String" Name="otherAttributeName2" />
                <Parameter Type="System.String" Name="otherAttributeName3" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute cannot be specified when attribute {2}, {3}, {4}, or {5} is also present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName1" />
                <Parameter Type="System.String" Name="otherAttributeName2" />
                <Parameter Type="System.String" Name="otherAttributeName3" />
                <Parameter Type="System.String" Name="otherAttributeName4" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeWithoutOtherAttributes" Number="37">
            <Instance>
                The {0}/@{1} attribute can only be specified with the following attribute {2} present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute can only be specified with one of the following attributes: {2} or {3} present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName1" />
                <Parameter Type="System.String" Name="otherAttributeName2" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute can only be specified with one of the following attributes: {2} or {3} present with value '{4}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName1" />
                <Parameter Type="System.String" Name="otherAttributeName2" />
                <Parameter Type="System.String" Name="otherAttributeValue" />
                <Parameter Type="System.Boolean" Name="uniquifier" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute can only be specified with one of the following attributes: {2}, {3}, or {4} present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName1" />
                <Parameter Type="System.String" Name="otherAttributeName2" />
                <Parameter Type="System.String" Name="otherAttributeName3" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute can only be specified with one of the following attributes: {2}, {3}, {4}, or {5} present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="otherAttributeName1" />
                <Parameter Type="System.String" Name="otherAttributeName2" />
                <Parameter Type="System.String" Name="otherAttributeName3" />
                <Parameter Type="System.String" Name="otherAttributeName4" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeValueWithoutOtherAttribute" Number="38">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', can only be specified with attribute {3} present with value '{4}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeValue" />
                <Parameter Type="System.String" Name="otherAttributeName" />
                <Parameter Type="System.String" Name="otherAttributeValue" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', cannot be specified without attribute {3} present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeValue" />
                <Parameter Type="System.String" Name="otherAttributeName" />
            </Instance>
        </Message>
        <Message Id="IntegralValueSentinelCollision" Number="39">
            <Instance>
                The integer value {0} collides with a sentinel value in the compiler code.
                <Parameter Type="System.Int32" Name="value" />
            </Instance>
            <Instance>
                The long integral value {0} collides with a sentinel value in the compiler code.
                <Parameter Type="System.Int64" Name="value" />
            </Instance>
        </Message>
        <Message Id="ExampleGuid" Number="40">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a legal Guid value.  A Guid needs to be generated and put in place of '{2}' in the source file.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="TooManyChildren" Number="41">
            <Instance>
                The {0} element contains multiple {1} child elements.  There can only be one {1} child element per {0} element.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="childElementName" />
            </Instance>
        </Message>
        <Message Id="ComponentMultipleKeyPaths" Number="42">
            <Instance>
                The {0} element has multiple key paths set.  The key path may only be set to '{2}' in extension elements that support it or one of the following locations: {0}/@{1}, {3}/@{1}, {4}/@{1}, or {5}/@{1}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="fileElementName" />
                <Parameter Type="System.String" Name="registryElementName" />
                <Parameter Type="System.String" Name="odbcDataSourceElementName" />
            </Instance>
        </Message>
        <Message Id="CabClosureFailed" Number="43" SourceLineNumbers="no">
            <Instance>
                Failed to close cab '{0}'.
                <Parameter Type="System.String" Name="cabinet" />
            </Instance>
            <Instance>
                Failed to close cab '{0}', error: {1}.
                <Parameter Type="System.String" Name="cabinet" />
                <Parameter Type="System.Int32" Name="error" />
            </Instance>
        </Message>
        <Message Id="ExpectedAttributes" Number="44">
            <Instance>
                The {0} element's {1} or {2} attribute was not found; one of these is required.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
            </Instance>
            <Instance>
                The {0} element's {1}, {2}, or {3} attribute was not found; one of these is required.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
                <Parameter Type="System.String" Name="attributeName3" />
            </Instance>
            <Instance>
                The {0} element's {1}, {2}, {3}, or {4} attribute was not found; one of these is required.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
                <Parameter Type="System.String" Name="attributeName3" />
                <Parameter Type="System.String" Name="attributeName4" />
            </Instance>
            <Instance>
                The {0} element's {1}, {2}, {3}, {4}, or {5} attribute was not found; one of these is required.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
                <Parameter Type="System.String" Name="attributeName3" />
                <Parameter Type="System.String" Name="attributeName4" />
                <Parameter Type="System.String" Name="attributeName5" />
            </Instance>
            <Instance>
                The {0} element's {1}, {2}, {3}, {4}, {5}, or {6} attribute was not found; one of these is required.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
                <Parameter Type="System.String" Name="attributeName3" />
                <Parameter Type="System.String" Name="attributeName4" />
                <Parameter Type="System.String" Name="attributeName5" />
                <Parameter Type="System.String" Name="attributeName6" />
            </Instance>
            <Instance>
                The {0} element's {1}, {2}, {3}, {4}, {5}, {6}, or {7} attribute was not found; one of these is required.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
                <Parameter Type="System.String" Name="attributeName3" />
                <Parameter Type="System.String" Name="attributeName4" />
                <Parameter Type="System.String" Name="attributeName5" />
                <Parameter Type="System.String" Name="attributeName6" />
                <Parameter Type="System.String" Name="attributeName7" />
            </Instance>
        </Message>
        <Message Id="ExpectedAttributesWithOtherAttribute" Number="45">
            <Instance>
                The {0} element's {1} or {2} attribute was not found; at least one of these attributes must be specified.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
            </Instance>
            <Instance>
                The {0} element's {1} or {2} attribute was not found; one of these is required when attribute {3} is present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
                <Parameter Type="System.String" Name="otherAttributeName" />
            </Instance>
            <Instance>
                The {0} element's {1} or {2} attribute was not found; one of these is required when attribute {3} has a value of '{4}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
                <Parameter Type="System.String" Name="otherAttributeName" />
                <Parameter Type="System.String" Name="otherAttributeValue" />
            </Instance>
        </Message>
        <Message Id="ExpectedAttributesWithoutOtherAttribute" Number="46">
            <Instance>
                The {0} element's {1} or {2} attribute was not found; one of these is required without attribute {3} present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
                <Parameter Type="System.String" Name="otherAttributeName" />
            </Instance>
        </Message>
        <Message Id="MissingTypeLibFile" Number="47">
            <Instance>
                The {0} element is non-advertised and therefore requires a parent {1} element.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="fileElementName" />
            </Instance>
        </Message>
        <Message Id="InvalidDocumentElement" Number="48">
            <Instance>
                The document element name '{0}' is invalid.  A Windows Installer XML {1} file must use '{2}' as the document element name.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="fileType" />
                <Parameter Type="System.String" Name="expectedElementName" />
            </Instance>
        </Message>
        <Message Id="ExpectedAttributeInElementOrParent" Number="49">
            <Instance>
                The {0}/@{1} attribute was not found or empty; it is required, or it can be specified in the parent {2} element.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="parentElementName" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute was not found or empty; it is required, or it can be specified in the parent {2}/@{3} attribute.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="parentElementName" />
                <Parameter Type="System.String" Name="parentAttributeName" />
            </Instance>
        </Message>
        <Message Id="UnauthorizedAccess" Number="50" SourceLineNumbers="no">
            <Instance>
                Access to the path '{0}' is denied.
                <Parameter Type="System.String" Name="filePath" />
            </Instance>
        </Message>
        <Message Id="IllegalModuleExclusionLanguageAttributes" Number="51">
            <Instance>Cannot set both ExcludeLanguage and ExcludeExceptLanguage attributes on a ModuleExclusion element.</Instance>
        </Message>
        <Message Id="NoFirstControlSpecified" Number="52">
            <Instance>
                The '{0}' dialog element does not have a valid tabbable control. You must either have a tabbable control that is not marked TabSkip='yes', or you must mark a control TabSkip='no'. If you have a page with no tabbable controls (a progress page, for example), you might want to set the first Text control to be TabSkip='no'.
                <Parameter Type="System.String" Name="dialogName" />
            </Instance>
        </Message>
        <Message Id="NoDataForColumn" Number="53">
            <Instance>
                There is no data for column '{0}' in a contained row of custom table '{1}'.  A non-null value must be supplied for this column.
                <Parameter Type="System.String" Name="columnName" />
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="ValueAndMaskMustBeSameLength" Number="54">
            <Instance>
                The FileTypeMask/@Value and FileTypeMask/@Mask attributes must be the same length.
            </Instance>
        </Message>
        <Message Id="TooManySearchElements" Number="55">
            <Instance>
                Only one search element can appear under a '{0}' element.
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeExceptOnElement" Number="56">
            <Instance>
                The {1} attribute can only be specified on the {2} element.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="expectedElementName" />
            </Instance>
        </Message>
        <Message Id="SearchElementRequired" Number="57">
            <Instance>
                A '{0}' element must have a search element as a child.
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
        </Message>
        <Message Id="MultipleIdentifiersFound" Number="58">
            <Instance>
                Under a '{0}' element, multiple identifiers were found: '{1}' and '{2}'.  All search elements under this element must have the same id.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="identifier" />
                <Parameter Type="System.String" Name="mismatchIdentifier" />
            </Instance>
        </Message>
        <Message Id="AdvertiseStateMustMatch" Number="59">
            <Instance>
                The advertise state of this element: '{0}', does not match the advertise state set on the parent element: '{1}'.
                <Parameter Type="System.String" Name="advertiseState" />
                <Parameter Type="System.String" Name="parentAdvertiseState" />
            </Instance>
        </Message>
        <Message Id="DuplicateContextValue" Number="60">
            <Instance>
                The context value '{0}' was duplicated. Context values must be distinct.
                <Parameter Type="System.String" Name="contextValue" />
            </Instance>
        </Message>
        <Message Id="RelativePathForRegistryElement" Number="61">
            <Instance>
                Cannot convert RelativePath into Registry elements.
            </Instance>
        </Message>
        <Message Id="IllegalAttributeWhenNested" Number="62">
            <Instance>
                The {0}/@{1} attribute cannot be specified when the {0} element is nested underneath a {2} element. If this {0} is a member of a ComponentGroup where ComponentGroup/@{1} is set, then the {0}/@{1} attribute should be removed.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="parentElement" />
            </Instance>
        </Message>
        <Message Id="ExpectedElement" Number="63">
            <Instance>
                A {0} element must have at least one child element of type {1}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="childName" />
            </Instance>
            <Instance>
                A {0} element must have at least one child element of type {1} or {2}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="childName1" />
                <Parameter Type="System.String" Name="childName2" />
            </Instance>
            <Instance>
                A {0} element must have at least one child element of type {1}, {2}, or {3}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="childName1" />
                <Parameter Type="System.String" Name="childName2" />
                <Parameter Type="System.String" Name="childName3" />
            </Instance>
            <Instance>
                A {0} element must have at least one child element of type {1}, {2}, {3}, or {4}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="childName1" />
                <Parameter Type="System.String" Name="childName2" />
                <Parameter Type="System.String" Name="childName3" />
                <Parameter Type="System.String" Name="childName4" />
            </Instance>
        </Message>
        <Message Id="RegistryRootInvalid" Number="64">
            <Instance>
                Registry/@Root attribute is invalid on a nested Registry element.  Either remove the Root attribute or move the Registry element so it is not nested under another Registry element.
            </Instance>
        </Message>
        <Message Id="IllegalYesNoDefaultValue" Number="65">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a legal yes/no/default value.  The only legal values are 'default', 'no' or 'yes'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeInMergeModule" Number="66">
            <Instance>
                The {0}/@{1} attribute cannot be specified in a merge module.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="GenericReadNotAllowed" Number="67">
            <Instance>Permission elements cannot have GenericRead as the only permission specified. Include at least one other permission.</Instance>
        </Message>
        <Message Id="IllegalAttributeWithInnerText" Number="68">
            <Instance>
                The {0}/@{1} attribute cannot be specified when the element has body text as well. Specify either the attribute or the body, but not both.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="SearchElementRequiredWithAttribute" Number="69">
            <Instance>
                A {0} element must have a search element as a child when the {0}/@{1} attribute has the value '{2}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeValue" />
            </Instance>
        </Message>
        <Message Id="CannotAuthorSpecialProperties" Number="70">
            <Instance>
                The {0} property was specified. Special MSI properties cannot be authored.  Use the attributes on the Property element instead.
                <Parameter Type="System.String" Name="propertyName" />
            </Instance>
        </Message>
        <Message Id="CannotSpecifySequenceAndOnExit" Number="71">
            <Instance>
                The sequence number for a {0} element can be specified at most once, with either a 'Sequence' or 'OnExit' attribute, but not both.
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
        </Message>
        <Message Id="NeedSequenceBeforeOrAfter" Number="72">
            <Instance>
                A {0} element must have a Before attribute, After attribute, or a Sequence attribute.
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
        </Message>
        <Message Id="ValueNotSupported" Number="73">
            <Instance>
                The {0}/@{1} attribute's value, '{2}, is not supported by the Windows Installer.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeValue" />
            </Instance>
        </Message>
        <Message Id="TabbableControlNotAllowedInBillboard" Number="74">
            <Instance>
                A {0} element was specified with Type='{1}' and TabSkip='no'. Tabbable controls are not allowed in Billboards.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="controlType" />
            </Instance>
        </Message>
        <Message Id="CheckBoxValueOnlyValidWithCheckBox" Number="75">
            <Instance>
                A {0} element was specified with Type='{1}' and a CheckBoxValue. Check box values can only be specified with Type='CheckBox'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="controlType" />
            </Instance>
        </Message>
        <Message Id="CabFileDoesNotExist" Number="76" SourceLineNumbers="no">
            <Instance>
                Attempted to extract cab '{0}' from merge module '{1}' to directory '{2}'. The cab file was not found. This usually means that you have a merge module without a cabinet inside it.
                <Parameter Type="System.String" Name="cabName" />
                <Parameter Type="System.String" Name="mergeModulePath" />
                <Parameter Type="System.String" Name="directoryName" />
            </Instance>
        </Message>
        <Message Id="RadioButtonTypeInconsistent" Number="77">
            <Instance>All RadioButton elements in a RadioButtonGroup must be consistent with their use of the Bitmap, Icon, and Text attributes. Ensure all of the RadioButton elements in this group have the same attribute specified.</Instance>
        </Message>
        <Message Id="RadioButtonBitmapAndIconDisallowed" Number="78">
            <Instance>RadioButtonGroup elements that contain RadioButton elements with Bitmap or Icon attributes set to "yes" can only be specified under a Control element.  Move your RadioButtonGroup element as a child of the appropriate Control element.</Instance>
        </Message>
        <Message Id="IllegalSuppressWarningId" Number="79" SourceLineNumbers="no">
            <Instance>
                Illegal value '{0}' for the -sw&lt;N&gt; command line option. Specify a particular warning number, like '-sw6' to suppress the warning with ID 6, or '-sw' alone to suppress all warnings.
                <Parameter Type="System.String" Name="suppressedId" />
            </Instance>
        </Message>
        <Message Id="PreprocessorIllegalForeachVariable" Number="80">
            <Instance>
                The variable named '{0}' is not allowed in a foreach expression.
                <Parameter Type="System.String" Name="variableName" />
            </Instance>
        </Message>
        <Message Id="PreprocessorMissingParameterPrefix" Number="81">
            <Instance>
                Could not find the prefix in parameter name: '{0}'.
                <Parameter Type="System.String" Name="parameterName" />
            </Instance>
        </Message>
        <Message Id="PreprocessorExtensionForParameterMissing" Number="82">
            <Instance>
                Could not find the preprocessor extension for parameter '{0}'.  A preprocessor extension is expected because the parameter prefix, '{1}', is not one of the standard types: 'env', 'res', 'sys', or 'var'.
                <Parameter Type="System.String" Name="parameterName" />
                <Parameter Type="System.String" Name="parameterPrefix" />
            </Instance>
        </Message>
        <Message Id="CannotFindFile" Number="83">
            <Instance>
                The file with id '{0}' and name '{1}' could not be found with source path: '{2}'.
                <Parameter Type="System.String" Name="fileId" />
                <Parameter Type="System.String" Name="fileName" />
                <Parameter Type="System.String" Name="filePath" />
            </Instance>
        </Message>
        <Message Id="BinderFileManagerMissingFile" Number="84">
            <Instance>
                {0}
                <Parameter Type="System.String" Name="exceptionMessage" />
            </Instance>
        </Message>
        <Message Id="InvalidFileName" Number="85">
            <Instance>
                Invalid file name '{0}'.
                <Parameter Type="System.String" Name="fileName" />
            </Instance>
        </Message>
        <Message Id="ReferenceLoopDetected" Number="86">
            <Instance>
                A circular reference of groups was detected. The infinite loop includes: {0}. Group references must form a directed acyclic graph.
                <Parameter Type="System.String" Name="loopList" />
            </Instance>
        </Message>
        <Message Id="GuidContainsLowercaseLetters" Number="87">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is a mixed-case guid.  All letters in a guid value should be uppercase.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="InvalidDateTimeFormat" Number="88">
            <Instance>
                The {0}/@{1} attribute's value '{2}' is not a valid date/time value. A date/time value should follow the format YYYY-MM-DDTHH:mm:ss.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="MultipleEntrySections" Number="89">
            <Instance>
                Multiple entry sections '{0}' and '{1}' found.  Only one entry section may be present in a single target.
                <Parameter Type="System.String" Name="sectionName1" />
                <Parameter Type="System.String" Name="sectionName2" />
            </Instance>
        </Message>
        <Message Id="MultipleEntrySections2" Number="90">
            <Instance>Location of entry section related to previous error.</Instance>
        </Message>
        <Message Id="DuplicateSymbol" Number="91">
            <Instance>
                Duplicate symbol '{0}' found. This typically means that an Id is duplicated. Check to make sure all your identifiers of a given type (File, Component, Feature) are unique.
                <Parameter Type="System.String" Name="symbolName" />
            </Instance>
        </Message>
        <Message Id="DuplicateSymbol2" Number="92">
            <Instance>Location of symbol related to previous error.</Instance>
        </Message>
        <Message Id="MissingEntrySection" Number="93" SourceLineNumbers="no">
            <Instance>
                Could not find entry section in provided list of intermediates. Expected section of type '{0}'.
                <Parameter Type="System.String" Name="sectionType" />
            </Instance>
        </Message>
        <Message Id="UnresolvedReference" Number="94">
            <Instance>
                Unresolved reference to symbol '{2}' in section '{0}:{1}'.
                <Parameter Type="System.String" Name="sectionType" />
                <Parameter Type="System.String" Name="sectionId" />
                <Parameter Type="System.String" Name="referencedSymbol" />
            </Instance>
        </Message>
        <Message Id="MultiplePrimaryReferences" Number="95">
            <Instance>
                Multiple primary references were found for {0} '{1}' in {2} '{3}' and {4} '{5}'.
                <Parameter Type="System.String" Name="crefChildType" />
                <Parameter Type="System.String" Name="crefChildId" />
                <Parameter Type="System.String" Name="crefParentType" />
                <Parameter Type="System.String" Name="crefParentId" />
                <Parameter Type="System.String" Name="conflictParentType" />
                <Parameter Type="System.String" Name="conflictParentId" />
            </Instance>
        </Message>
        <Message Id="ComponentReferencedTwice" Number="96">
            <Instance>
                Component {0} cannot be contained in a Module twice.
                <Parameter Type="System.String" Name="crefChildId" />
            </Instance>
        </Message>
        <Message Id="DuplicateModuleFileIdentifier" Number="97">
            <Instance>
                The merge module '{0}' contains a file identifier, '{1}', that is duplicated either in another merge module or in a File/@Id attribute.  File identifiers must be unique.  Please change one of the file identifiers to a different value.
                <Parameter Type="System.String" Name="moduleId" />
                <Parameter Type="System.String" Name="fileId" />
            </Instance>
        </Message>
        <Message Id="DuplicateModuleCaseInsensitiveFileIdentifier" Number="98">
            <Instance>
                The merge module '{0}' contains 2 or more file identifiers that only differ by case: '{1}' and '{2}'.  The Windows Installer XML toolset extracts merge module files to the file system using these identifiers.  Since most file systems are not case-sensitive a collision is likely.  Please contact the owner of the merge module for a fix.
                <Parameter Type="System.String" Name="moduleId" />
                <Parameter Type="System.String" Name="fileId1" />
                <Parameter Type="System.String" Name="fileId2" />
            </Instance>
        </Message>
        <Message Id="ImplicitComponentKeyPath" Number="99">
            <Instance>
                The component '{0}' does not have an explicit key path specified.  If the ordering of the elements under the Component element changes, the key path will also change.  To prevent accidental changes, the key path should be set to 'yes' in one of the following locations: Component/@KeyPath, File/@KeyPath, ODBCDataSource/@KeyPath, or Registry/@KeyPath.
                <Parameter Type="System.String" Name="componentId" />
            </Instance>
        </Message>
        <Message Id="DuplicateLocalizationIdentifier" Number="100">
            <Instance>
                The localization identifier '{0}' has been duplicated in multiple locations.  Please resolve the conflict.
                <Parameter Type="System.String" Name="localizationId" />
            </Instance>
        </Message>
        <Message Id="LocalizationVariableUnknown" Number="102">
            <Instance>
                The localization variable !(loc.{0}) is unknown.  Please ensure the variable is defined.
                <Parameter Type="System.String" Name="variableId" />
            </Instance>
        </Message>
        <Message Id="FileNotFound" Number="103">
            <Instance>
                The system cannot find the file '{0}'.
                <Parameter Type="System.String" Name="file" />
            </Instance>
            <Instance>
                The system cannot find the file '{0}' with type '{1}'.
                <Parameter Type="System.String" Name="file" />
                <Parameter Type="System.String" Name="fileType" />
            </Instance>
        </Message>
        <Message Id="InvalidXml" Number="104">
            <Instance>
                Not a valid {0} file; detail: {1}
                <Parameter Type="System.String" Name="fileType" />
                <Parameter Type="System.String" Name="detail" />
            </Instance>
        </Message>
        <Message Id="ProgIdNestedTooDeep" Number="105">
            <Instance>ProgId elements may not be nested more than 1 level deep.</Instance>
        </Message>
        <Message Id="CanNotHaveTwoParents" Number="106">
            <Instance>
                The DirectorySearchRef {0} can not have a Parent attribute {1} and also be nested under parent element {2}
                <Parameter Type="System.String" Name="directorySearch" />
                <Parameter Type="System.String" Name="parentAttribute" />
                <Parameter Type="System.String" Name="parentElement" />
            </Instance>
        </Message>
        <Message Id="SchemaValidationFailed" Number="107">
            <Instance>
                Schema validation failed with the following error at line {1}, column {2}: {0}
                <Parameter Type="System.String" Name="validationError" />
                <Parameter Type="System.Int32" Name="lineNumber" />
                <Parameter Type="System.Int32" Name="linePosition" />
            </Instance>
        </Message>
        <Message Id="IllegalVersionValue" Number="108">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a valid version.  Legal version values should look like 'x.x.x.x' where x is an integer from 0 to 65534.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="CustomTableNameTooLong" Number="109">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is too long for a table name.  It cannot be more than than 31 characters long.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="CustomTableIllegalColumnWidth" Number="110">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a valid column width.  Valid column widths are 2 or 4.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.Int32" Name="value" />
            </Instance>
        </Message>
        <Message Id="CustomTableMissingPrimaryKey" Number="111">
            <Instance>The CustomTable is missing a Column element with the PrimaryKey attribute set to 'yes'.  At least one column must be marked as the primary key.</Instance>
        </Message>
        <Message Id="TypeSpecificationForExtensionRequired" Number="113" SourceLineNumbers="no">
            <Instance>
                The parameter '{0}' must be followed by the extension's type specification.  The type specification should be a fully qualified class and assembly identity, for example: "MyNamespace.MyClass,myextension.dll".
                <Parameter Type="System.String" Name="parameter" />
            </Instance>
        </Message>
        <Message Id="FilePathRequired" SourceLineNumbers="no" Number="114">
            <Instance>
                The parameter '{0}' must be followed by a file path.
                <Parameter Type="System.String" Name="parameter" />
            </Instance>
        </Message>
        <Message Id="DirectoryPathRequired" Number="115" SourceLineNumbers="no">
            <Instance>
                The parameter '{0}' must be followed by a directory path.
                <Parameter Type="System.String" Name="parameter" />
            </Instance>
        </Message>
        <Message Id="FileOrDirectoryPathRequired" Number="116" SourceLineNumbers="no">
            <Instance>
                The parameter '{0}' must be followed by a file or directory path.  To specify a directory path the string must end with a backslash, for example: "C:\Path\".
                <Parameter Type="System.String" Name="parameter" />
            </Instance>
        </Message>
        <Message Id="PathCannotContainQuote" Number="117" SourceLineNumbers="no">
            <Instance>
                Path '{0}' contains a literal quote character. Quotes are often accidentally introduced when trying to refer to a directory path with spaces in it, such as "C:\Out Directory\" -- the backslash before the quote acts an escape character. The correct representation for that path is: "C:\Out Directory\\".
                <Parameter Type="System.String" Name="fileName" />
            </Instance>
        </Message>
        <Message Id="AdditionalArgumentUnexpected" Number="118" SourceLineNumbers="no">
            <Instance>
                Additional argument '{0}' was unexpected.  Remove the argument and add the '-?' switch for more information.
                <Parameter Type="System.String" Name="argument" />
            </Instance>
        </Message>
        <Message Id="RegistryNameValueIncorrect" Number="119">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is incorrect.  It should not contain values of '+', '-', or '*' when the {0}/@Value attribute is empty.  Instead, use the proper element and attributes: for Name='+' use RegistryKey/@Action='createKey', for Name='-' use RemoveRegistryKey/@Action='removeOnUninstall', for Name='*' use RegistryKey/@Action='createAndRemoveOnUninstall'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="FamilyNameTooLong" Number="120">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is {3} characters long.  This is too long for a family name because the maximum allowed length is 8 characters long.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.Int32" Name="length" />
            </Instance>
        </Message>
        <Message Id="IllegalFamilyName" Number="121">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', contains illegal characters for a family name.  Legal values include letters, numbers, and underscores.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="IllegalLongValue" Number="122">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a legal long value.  Legal long values are from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="IntegralValueOutOfRange" Number="123">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not in the range of legal values.  Legal values for this attribute are from {3} to {4}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.Int32" Name="value" />
                <Parameter Type="System.Int32" Name="minimum" />
                <Parameter Type="System.Int32" Name="maximum" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not in the range of legal values.  Legal values for this attribute are from {3} to {4}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.Int64" Name="value" />
                <Parameter Type="System.Int64" Name="minimum" />
                <Parameter Type="System.Int64" Name="maximum" />
            </Instance>
        </Message>
        <Message Id="DuplicateExtensionXmlSchemaNamespace" Number="125" SourceLineNumbers="no">
            <Instance>
                The extension '{0}' uses the same xml schema namespace, '{1}', as previously loaded extension '{2}'.  Please either remove one of the extensions or rename the xml schema namespace to avoid the collision.
                <Parameter Type="System.String" Name="extension" />
                <Parameter Type="System.String" Name="extensionXmlSchemaNamespace" />
                <Parameter Type="System.String" Name="collidingExtension" />
            </Instance>
        </Message>
        <Message Id="DuplicateExtensionTable" Number="126" SourceLineNumbers="no">
            <Instance>
                The extension '{0}' contains a defintion for table '{1}' that collides with a previously loaded table definition.  Please remove one of the conflicting extensions or rename one of the tables to avoid the collision.
                <Parameter Type="System.String" Name="extension" />
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="DuplicateExtensionPreprocessorType" Number="127" SourceLineNumbers="no">
            <Instance>
                The extension '{0}' uses the same preprocessor variable prefix, '{1}', as previously loaded extension '{2}'.  Please remove one of the extensions or rename the prefix to avoid the collision.
                <Parameter Type="System.String" Name="extension" />
                <Parameter Type="System.String" Name="variablePrefix" />
                <Parameter Type="System.String" Name="collidingExtension" />
            </Instance>
        </Message>
        <Message Id="FileInUse" Number="128">
            <Instance>
                The process can not access the file '{0}' because it is being used by another process.
                <Parameter Type="System.String" Name="file" />
            </Instance>
        </Message>
        <Message Id="CannotOpenMergeModule" Number="129">
            <Instance>
                Cannot open the merge module '{0}' from file '{1}'.
                <Parameter Type="System.String" Name="mergeModuleIdentifier" />
                <Parameter Type="System.String" Name="mergeModuleFile" />
            </Instance>
        </Message>
        <Message Id="DuplicatePrimaryKey" Number="130">
            <Instance>
                The primary key '{0}' is duplicated in table '{1}'.  Please remove one of the entries or rename a part of the primary key to avoid the collision.
                <Parameter Type="System.String" Name="primaryKey" />
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="FileIdentifierNotFound" Number="131">
            <Instance>
                The file row with identifier '{0}' could not be found.
                <Parameter Type="System.String" Name="fileIdentifier" />
            </Instance>
        </Message>
        <Message Id="InvalidAssemblyFile" Number="132">
            <Instance>
                The assembly file '{0}' appears to be invalid.  Please ensure this is a valid assembly file and that the user has the appropriate access rights to this file.  More information: {1}
                <Parameter Type="System.String" Name="assemblyFile" />
                <Parameter Type="System.String" Name="moreInformation" />
            </Instance>
        </Message>
        <Message Id="ExpectedEndElement" Number="133">
            <Instance>
                The end element matching the '{0}' start element was not found.
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
        </Message>
        <Message Id="IllegalCodepage" Number="134" SourceLineNumbers="no">
            <Instance>
                The code page '{0}' is not a valid Windows code page. Update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage.
                <Parameter Type="System.Int32" Name="codepage" />
            </Instance>
        </Message>
        <Message Id="ExpectedMediaCabinet" Number="135">
            <Instance>
                The file '{0}' should be compressed but is not part of a compressed media. Files will be compressed if either the File/@Compressed or Package/@Compressed attributes are set to 'yes'.  This can be fixed by setting the Media/@Cabinet attribute for media '{1}'.
                <Parameter Type="System.String" Name="fileId" />
                <Parameter Type="System.Int32" Name="diskId" />
            </Instance>
        </Message>
        <Message Id="InvalidIdt" Number="136">
            <Instance>
                There was an error importing the file '{0}'.
                <Parameter Type="System.String" Name="idtFile" />
            </Instance>
            <Instance>
                There was an error importing table '{1}' from file '{0}'.
                <Parameter Type="System.String" Name="idtFile" />
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="InvalidSequenceTable" Number="137" SourceLineNumbers="no">
            <Instance>
                Found an invalid sequence table '{0}'.
                <Parameter Type="System.String" Name="sequenceTableName" />
            </Instance>
        </Message>
        <Message Id="ExpectedDirectory" Number="138" SourceLineNumbers="no">
            <Instance>
                The directory '{0}' could not be found.
                <Parameter Type="System.String" Name="directory" />
            </Instance>
        </Message>
        <Message Id="ComponentExpectedFeature" Number="139">
            <Instance>
                The component '{0}' is not assigned to a feature.  The component's {1} '{2}' requires it to be assigned to at least one feature.
                <Parameter Type="System.String" Name="component" />
                <Parameter Type="System.String" Name="type" />
                <Parameter Type="System.String" Name="target" />
            </Instance>
        </Message>
        <Message Id="RecursiveAction" Number="140" SourceLineNumbers="no">
            <Instance>
                The action '{0}' is recursively placed in the '{1}' table.
                <Parameter Type="System.String" Name="action" />
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="VersionMismatch" Number="141">
            <Instance>
                The {0} file format version {1} is not compatible with the expected {0} file format version {2}.
                <Parameter Type="System.String" Name="fileType" />
                <Parameter Type="System.String" Name="version" />
                <Parameter Type="System.String" Name="expectedVersion" />
            </Instance>
        </Message>
        <Message Id="UnexpectedContentNode" Number="142">
            <Instance>
                The {0} element contains an unexpected xml node of type {1}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="unexpectedNodeType" />
            </Instance>
        </Message>
        <Message Id="UnexpectedColumnCount" Number="143">
            <Instance>
                A parsed row has more fields that contain data for table '{0}' than are defined. This is potentially because a standard table is being redefined as a custom table or is based on an older table schema.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="InvalidExtension" Number="144" SourceLineNumbers="no">
            <Instance>
                The extension '{0}' could not be loaded.
                <Parameter Type="System.String" Name="extension" />
            </Instance>
            <Instance>
                The extension '{0}' could not be loaded because of the following reason: {1}
                <Parameter Type="System.String" Name="extension" />
                <Parameter Type="System.String" Name="invalidReason" />
            </Instance>
            <Instance>
                The extension '{0}' is the wrong type: '{1}'.  The expected type was '{2}'.
                <Parameter Type="System.String" Name="extension" />
                <Parameter Type="System.String" Name="extensionType" />
                <Parameter Type="System.String" Name="expectedType" />
            </Instance>
            <Instance>
                The extension '{0}' is the wrong type: '{1}'.  The expected type was '{2}' or '{3}'.
                <Parameter Type="System.String" Name="extension" />
                <Parameter Type="System.String" Name="extensionType" />
                <Parameter Type="System.String" Name="expectedType1" />
                <Parameter Type="System.String" Name="expectedType2" />
            </Instance>
        </Message>
        <Message Id="InvalidSubExpression" Number="145">
            <Instance>
                Found invalid subexpression '{0}' in expression '{1}'.
                <Parameter Type="System.String" Name="subExpression" />
                <Parameter Type="System.String" Name="expression" />
            </Instance>
        </Message>
        <Message Id="UnmatchedPreprocessorInstruction" Number="146">
            <Instance>
                Found a &lt;?{1}?&gt; processing instruction without a matching &lt;?{0}?&gt; before it.
                <Parameter Type="System.String" Name="beginInstruction" />
                <Parameter Type="System.String" Name="endInstruction" />
            </Instance>
        </Message>
        <Message Id="NonterminatedPreprocessorInstruction" Number="147">
            <Instance>
                Found a &lt;?{0}?&gt; processing instruction without a matching &lt;?{1}?&gt; after it.
                <Parameter Type="System.String" Name="beginInstruction" />
                <Parameter Type="System.String" Name="endInstruction" />
            </Instance>
        </Message>
        <Message Id="ExpectedExpressionAfterNot" Number="148">
            <Instance>
                Expecting an argument for 'NOT' in expression '{0}'.
                <Parameter Type="System.String" Name="expression" />
            </Instance>
        </Message>
        <Message Id="InvalidPreprocessorVariable" Number="149">
            <Instance>
                Ill-formed preprocessor variable '$({0})'.  Variables must have a prefix (like 'var.', 'env.', or 'sys.') and a name at least 1 character long. If the literal string '$({0})' is desired, use '$$({0})'.
                <Parameter Type="System.String" Name="variable" />
            </Instance>
        </Message>
        <Message Id="UndefinedPreprocessorVariable" Number="150">
            <Instance>
                Undefined preprocessor variable '$({0})'.
                <Parameter Type="System.String" Name="variableName" />
            </Instance>
        </Message>
        <Message Id="IllegalDefineStatement" Number="151">
            <Instance>
                The define statement '&lt;?define {0}?&gt;' is not well-formed.  Define statements should be in the form &lt;?define variableName = "variable value"?&gt;.
                <Parameter Type="System.String" Name="defineStatement" />
            </Instance>
        </Message>
        <Message Id="VariableDeclarationCollision" Number="152">
            <Instance>
                The variable '{0}' with value '{1}' was previously declared with value '{2}'.
                <Parameter Type="System.String" Name="variableName" />
                <Parameter Type="System.String" Name="variableValue" />
                <Parameter Type="System.String" Name="variableCollidingValue" />
            </Instance>
        </Message>
        <Message Id="CannotReundefineVariable" Number="153">
            <Instance>
                The variable '{0}' cannot be undefined because its already undefined.
                <Parameter Type="System.String" Name="variableName" />
            </Instance>
        </Message>
        <Message Id="IllegalForeach" Number="154">
            <Instance>
                The foreach statement '{0}' is illegal.  The proper format for foreach is &lt;?foreach varName in valueList?&gt;.
                <Parameter Type="System.String" Name="foreachStatement" />
            </Instance>
        </Message>
        <Message Id="IllegalParentAttributeWhenNested" Number="155">
            <Instance>
                The {0}/@{1} attribute cannot be specified when a {2} element is nested underneath the {0} element.
                <Parameter Type="System.String" Name="parentElementName" />
                <Parameter Type="System.String" Name="parentAttributeName" />
                <Parameter Type="System.String" Name="childElement" />
            </Instance>
        </Message>
        <Message Id="ExpectedEndforeach" Number="156">
            <Instance>A &lt;?foreach?&gt; statement was found that had no matching &lt;?endforeach?&gt;.</Instance>
        </Message>
        <Message Id="UnmatchedQuotesInExpression" Number="158">
            <Instance>
                The quotes don't match in the expression '{0}'.
                <Parameter Type="System.String" Name="expression" />
            </Instance>
        </Message>
        <Message Id="UnmatchedParenthesisInExpression" Number="159">
            <Instance>
                The parenthesis don't match in the expression '{0}'.
                <Parameter Type="System.String" Name="expression" />
            </Instance>
        </Message>
        <Message Id="ExpectedVariable" Number="160">
            <Instance>
                A required variable was missing in the expression '{0}'.
                <Parameter Type="System.String" Name="expression" />
            </Instance>
        </Message>
        <Message Id="UnexpectedLiteral" Number="161">
            <Instance>
                An unexpected literal was found in the expression '{0}'.
                <Parameter Type="System.String" Name="expression" />
            </Instance>
        </Message>
        <Message Id="IllegalIntegerInExpression" Number="162">
            <Instance>
                An illegal number was found in the expression '{0}'.
                <Parameter Type="System.String" Name="expression" />
            </Instance>
        </Message>
        <Message Id="UnexpectedPreprocessorOperator" Number="163">
            <Instance>
                The operator '{0}' is unexpected.
                <Parameter Type="System.String" Name="operator" />
            </Instance>
        </Message>
        <Message Id="UnexpectedEmptySubexpression" Number="164">
            <Instance>
                The empty subexpression is unexpected in the expression '{0}'.
                <Parameter Type="System.String" Name="expression" />
            </Instance>
        </Message>
        <Message Id="UnexpectedCustomTableColumn" Number="165">
            <Instance>
                The custom table column '{0}' is unknown.
                <Parameter Type="System.String" Name="column" />
            </Instance>
        </Message>
        <Message Id="UnknownCustomTableColumnType" Number="166">
            <Instance>
                Encountered an unknown custom table column type '{0}'.
                <Parameter Type="System.String" Name="columnType" />
            </Instance>
        </Message>
        <Message Id="IllegalFileCompressionAttributes" Number="167">
            <Instance>Cannot have both the MsidbFileAttributesCompressed and MsidbFileAttributesNoncompressed options set in a file attributes column.</Instance>
        </Message>
        <Message Id="OverridableActionCollision" Number="168">
            <Instance>
                The {0} table contains an action '{1}' that is declared overridable in two different locations.  Please remove one of the actions or the Overridable='yes' attribute from one of the actions.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName" />
            </Instance>
        </Message>
        <Message Id="OverridableActionCollision2" Number="169">
            <Instance>The location of the action related to previous error.</Instance>
        </Message>
        <Message Id="ActionCollision" Number="170">
            <Instance>
                The {0} table contains an action '{1}' that is declared in two different locations.  Please remove one of the actions or set the Overridable='yes' attribute on one of their elements.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName" />
            </Instance>
        </Message>
        <Message Id="ActionCollision2" Number="171">
            <Instance>The location of the action related to previous error.</Instance>
        </Message>
        <Message Id="SuppressNonoverridableAction" Number="172">
            <Instance>
                The {0} table contains an action '{1}' that cannot be suppressed because it is not declared overridable in the base definition.  Please stop suppressing the action or make it overridable in its base declaration.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName" />
            </Instance>
        </Message>
        <Message Id="SuppressNonoverridableAction2" Number="173">
            <Instance>The location of the non-overridable definition of the action related to previous error.</Instance>
        </Message>
        <Message Id="CustomActionSequencedInModule" Number="174">
            <Instance>
                The {0} table contains a custom action '{1}' that has a sequence number specified.  The Sequence attribute is not allowed for custom actions in a merge module.  Please remove the action or use the Before or After attributes to specify where this action should be sequenced relative to another action.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName" />
            </Instance>
        </Message>
        <Message Id="StandardActionRelativelyScheduledInModule" Number="175">
            <Instance>
                The {0} table contains a standard action '{1}' that does not have a sequence number specified.  The Sequence attribute is required for standard actions in a merge module.  Please remove the action or use the Sequence attribute.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName" />
            </Instance>
        </Message>
        <Message Id="ActionCircularDependency" Number="176">
            <Instance>
                The {0} table contains an action '{1}' that is scheduled to come before or after action '{2}', which is also scheduled to come before or after action '{1}'.  Please remove this circular dependency by changing the Before or After attribute for one of the actions.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName1" />
                <Parameter Type="System.String" Name="actionName2" />
            </Instance>
        </Message>
        <Message Id="ActionScheduledRelativeToTerminationAction" Number="177">
            <Instance>
                The {0} table contains an action '{1}' that is scheduled to come before or after action '{2}', which is a special action which only occurs when the installer terminates.  These special actions can be identified by their negative sequence numbers.  Please schedule the action '{1}' to come before or after a different action.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName1" />
                <Parameter Type="System.String" Name="actionName2" />
            </Instance>
        </Message>
        <Message Id="ActionScheduledRelativeToTerminationAction2" Number="178">
            <Instance>The location of the special termination action related to previous error(s).</Instance>
        </Message>
        <Message Id="NoUniqueActionSequenceNumber" Number="179">
            <Instance>
                The {0} table contains an action '{1}' which cannot have a unique sequence number because it is scheduled before or after action '{2}'.  There is not enough room before or after this action to assign a unique sequence number.  Please schedule one of the actions differently so that it will be in a position with more sequence numbers available.  Please note that sequence numbers must be an integer in the range 1 - 32767 (inclusive).
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName1" />
                <Parameter Type="System.String" Name="actionName2" />
            </Instance>
        </Message>
        <Message Id="NoUniqueActionSequenceNumber2" Number="180">
            <Instance>The location of the sequenced action related to previous error.</Instance>
        </Message>
        <Message Id="ActionScheduledRelativeToItself" Number="181">
            <Instance>
                The {0}/@{1} attribute's value '{2}' is invalid because it would make this action dependent upon itself.  Please change the value to the name of a different action.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeValue" />
            </Instance>
        </Message>
        <Message Id="MissingTableDefinition" Number="182" SourceLineNumbers="no">
            <Instance>
                Cannot find the table definitions for the '{0}' table.  This is likely due to a typing error or missing extension.  Please ensure all the necessary extensions are supplied on the command line with the -ext parameter.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="ExpectedRowInPatchCreationPackage" Number="183" SourceLineNumbers="no">
            <Instance>
                Could not find a row in the '{0}' table for this patch creation package.  Patch creation packages must contain at least one row in the '{0}' table.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="UnexpectedTableInMergeModule" Number="184">
            <Instance>
                An unexpected row in the '{0}' table was found in this merge module.  Merge modules cannot contain the '{0}' table.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="UnexpectedTableInPatchCreationPackage" Number="185">
            <Instance>
                An unexpected row in the '{0}' table was found in this patch creation package.  Patch creation packages cannot contain the '{0}' table.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="MergeExcludedModule" Number="186">
            <Instance>
                The module '{0}' cannot be merged because it excludes or is excluded by the merge module with signature '{1}'.
                <Parameter Type="System.String" Name="mergeId" />
                <Parameter Type="System.String" Name="otherMergeId" />
            </Instance>
        </Message>
        <Message Id="MergeFeatureRequired" Number="187">
            <Instance>
                The {0} table contains a row with primary key(s) '{1}' which requires a feature to properly merge from the merge module '{2}'.  Nest a MergeRef element with an Id attribute set to the value '{3}' under a Feature element to fix this error.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="primaryKeys" />
                <Parameter Type="System.String" Name="mergeModuleFile" />
                <Parameter Type="System.String" Name="mergeId" />
            </Instance>
        </Message>
        <Message Id="MergeLanguageFailed" Number="188">
            <Instance>
                The language '{0}' is supported but uses an invalid language transform in the merge module '{1}'.
                <Parameter Type="System.Int16" Name="language" />
                <Parameter Type="System.String" Name="mergeModuleFile" />
            </Instance>
        </Message>
        <Message Id="MergeLanguageUnsupported" Number="189">
            <Instance>
                Could not locate language '{0}' (or a transform for this language) in the merge module '{1}'.  This is likely due to an incorrectly authored Merge/@Language attribute.
                <Parameter Type="System.Int16" Name="language" />
                <Parameter Type="System.String" Name="mergeModuleFile" />
            </Instance>
        </Message>
        <Message Id="TableDecompilationUnimplemented" Number="190" SourceLineNumbers="no">
            <Instance>
                Decompilation of the {0} table has not been implemented by its extension.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="CannotDefaultMismatchedAdvertiseStates" Number="191">
            <Instance>
                MIME element cannot be marked as the default when its advertise state differs from its parent element.  Ensure that the advertise state of the MIME element matches its parents element or remove the Mime/@Advertise attribute completely.
            </Instance>
        </Message>
        <Message Id="VersionIndependentProgIdsCannotHaveIcons" Number="192">
            <Instance>
                Version independent ProgIds cannot have Icons.  Remove the Icon and/or IconIndex attributes from your ProgId element.
            </Instance>
        </Message>
        <Message Id="IllegalAttributeValueWithOtherAttribute" Number="193">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', cannot be specified with attribute {3} present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeValue" />
                <Parameter Type="System.String" Name="otherAttributeName" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute's value, '{2}', cannot be specified with attribute {3} present with value '{4}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeValue" />
                <Parameter Type="System.String" Name="otherAttributeName" />
                <Parameter Type="System.String" Name="otherAttributeValue" />
            </Instance>
        </Message>
        <Message Id="InvalidMergeLanguage" Number="194">
            <Instance>
                The Merge element '{0}' specified an invalid language '{1}'.  Verify that localization tokens are being properly resolved to a numeric LCID.
                <Parameter Type="System.String" Name="mergeId" />
                <Parameter Type="System.String" Name="mergeLanguage" />
            </Instance>
        </Message>
        <Message Id="WixVariableCollision" Number="195">
            <Instance>
                The Windows Installer XML variable '{0}' is declared in more than one location.  Please remove one of the declarations.
                <Parameter Type="System.String" Name="variableId" />
            </Instance>
        </Message>
        <Message Id="ExpectedWixVariableValue" Number="196" SourceLineNumbers="no">
            <Instance>
                The Windows Installer XML variable '{0}' was declared without a value.  Please specify a value for the variable.
                <Parameter Type="System.String" Name="variableId" />
            </Instance>
        </Message>
        <Message Id="WixVariableUnknown" Number="197">
            <Instance>
                The Windows Installer XML variable !(wix.{0}) is unknown.  Please ensure the variable is declared on the command line for light.exe, via a WixVariable element, or inline using the syntax !(wix.{0}=some value which doesn't contain parenthesis).
                <Parameter Type="System.String" Name="variableId" />
            </Instance>
        </Message>
        <Message Id="IllegalWixVariablePrefix" Number="198">
            <Instance>
                The Windows Installer XML variable $(wix.{0}) uses an illegal prefix '$'.  Please use the '!' prefix instead.
                <Parameter Type="System.String" Name="variableId" />
            </Instance>
        </Message>
        <Message Id="InvalidWixXmlNamespace" Number="199">
            <Instance>
                The {0} element has no namespace.  Please make the {0} element look like the following: &lt;{0} xmlns="{1}"&gt;.
                <Parameter Type="System.String" Name="wixElementName" />
                <Parameter Type="System.String" Name="wixNamespace" />
            </Instance>
            <Instance>
                The {0} element has an incorrect namespace of '{1}'.  Please make the {0} element look like the following: &lt;{0} xmlns="{2}"&gt;.
                <Parameter Type="System.String" Name="wixElementName" />
                <Parameter Type="System.String" Name="elementNamespace" />
                <Parameter Type="System.String" Name="wixNamespace" />
            </Instance>
        </Message>
        <Message Id="UnhandledExtensionElement" Number="200">
            <Instance>
                The {0} element contains an unhandled extension element '{1}'.  Please ensure that the extension for elements in the '{2}' namespace has been provided.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="extensionElementName" />
                <Parameter Type="System.String" Name="extensionNamespace" />
            </Instance>
        </Message>
        <Message Id="UnhandledExtensionAttribute" Number="201">
            <Instance>
                The {0} element contains an unhandled extension attribute '{1}'.  Please ensure that the extension for attributes in the '{2}' namespace has been provided.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="extensionAttributeName" />
                <Parameter Type="System.String" Name="extensionNamespace" />
            </Instance>
        </Message>
        <Message Id="UnsupportedExtensionAttribute" Number="202">
            <Instance>
                The {0} element contains an unsupported extension attribute '{1}'.  The {0} element does not currently support extension attributes. Is the {1} attribute using the correct XML namespace?
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="extensionElementName" />
            </Instance>
        </Message>
        <Message Id="UnsupportedExtensionElement" Number="203">
            <Instance>
                The {0} element contains an unsupported extension element '{1}'.  The {0} element does not currently support extension elements. Is the {1} element using the correct XML namespace?
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="extensionElementName" />
            </Instance>
        </Message>
        <Message Id="ValidationError" Number="204">
            <Instance>
                {0}: {1}
                <Parameter Type="System.String" Name="ice" />
                <Parameter Type="System.String" Name="message" />
            </Instance>
        </Message>
        <Message Id="IllegalRootDirectory" Number="205">
            <Instance>
                The Directory with Id '{0}' is not a valid root directory.  There may only be a single root directory per product or module and its Id attribute value must be 'TARGETDIR' and its Name attribute value must be 'SourceDir'.
                <Parameter Type="System.String" Name="directoryId" />
            </Instance>
        </Message>
        <Message Id="IllegalTargetDirDefaultDir" Number="206">
            <Instance>
                The 'TARGETDIR' directory has an illegal DefaultDir value of '{0}'.  The DefaultDir value is created from the *Name attributes of the Directory element.  The TARGETDIR directory is a special directory which must have its Name attribute set to 'SourceDir'.
                <Parameter Type="System.String" Name="defaultDir" />
            </Instance>
        </Message>
        <Message Id="TooManyElements" Number="207">
            <Instance>
                The {0} element contains an unexpected child element '{1}'.  The '{1}' element may only occur {2} time(s) under the {0} element.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="childElementName" />
                <Parameter Type="System.Int32" Name="expectedInstances" />
            </Instance>
        </Message>
        <Message Id="ExpectedBinaryCategory" Number="208">
            <Instance>The Column element specifies a binary column but does not have the correct Category specified.  Windows Installer requires binary columns to specify their category as binary.  Please set the Category attribute's value to 'Binary'.</Instance>
        </Message>
        <Message Id="RootFeatureCannotFollowParent" Number="209">
            <Instance>The Feature element specifies a root feature with an illegal InstallDefault value of 'followParent'.  Root features cannot follow their parent feature's install state because they don't have a parent feature.  Please remove or change the value of the InstallDefault attribute.</Instance>
        </Message>
        <Message Id="FeatureNameTooLong" Number="210">
            <Instance>
                The {0}/@{1} attribute with value '{2}', is too long for a feature name.  Due to limitations in the Windows Installer, feature names cannot be longer than 38 characters in length.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeValue" />
            </Instance>
        </Message>
        <Message Id="SignedEmbeddedCabinet" Number="211">
            <Instance>The DigitalSignature element cannot be nested under a Media element which specifies EmbedCab='yes'.  This is because Windows Installer can only verify the digital signatures of external cabinets.  Please either remove the DigitalSignature element or change the value of the Media/@EmbedCab attribute to 'no'.</Instance>
        </Message>
        <Message Id="ExpectedSignedCabinetName" Number="212">
            <Instance>The Media/@Cabinet attribute was not found; it is required when this element contains a DigitalSignature child element.  This is because Windows Installer can only verify the digital signatures of external cabinets.  Please either remove the DigitalSignature element or specify a valid external cabinet name via the Cabinet attribute.</Instance>
        </Message>
        <Message Id="IllegalInlineLocVariable" Number="213">
            <Instance>
                The localization variable '{0}' specifies an illegal inline default value of '{1}'.  Localization variables cannot specify default values inline, instead the value should be specified in a Windows Installer XML localization (.wxl) file.
                <Parameter Type="System.String" Name="variableName" />
                <Parameter Type="System.String" Name="variableValue" />
            </Instance>
        </Message>
        <Message Id="MergeModuleExpectedFeature" Number="215">
            <Instance>
                The merge module '{0}' is not assigned to a feature.  All merge modules must be assigned to at least one feature.
                <Parameter Type="System.String" Name="mergeId" />
            </Instance>
        </Message>
        <Message Id="Win32Exception" Number="216" SourceLineNumbers="no">
            <Instance>
                An unexpected Win32 exception with error code 0x{0:X} occurred: {1}
                <Parameter Type="System.Int32" Name="nativeErrorCode"/>
                <Parameter Type="System.String" Name="message" />
            </Instance>
            <Instance>
                An unexpected Win32 exception with error code 0x{0:X} occurred while accessing file '{1}': {2}
                <Parameter Type="System.Int32" Name="nativeErrorCode"/>
                <Parameter Type="System.String" Name="file"/>
                <Parameter Type="System.String" Name="message" />
            </Instance>
        </Message>
        <Message Id="UnexpectedExternalUIMessage" Number="217" SourceLineNumbers="no">
            <Instance>
                Error executing unknown ICE action. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: &quot;{0}&quot;.
                <Parameter Type="System.String" Name="message" />
            </Instance>
            <Instance>
                Error executing ICE action '{1}'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: &quot;{0}&quot;.
                <Parameter Type="System.String" Name="message" />
                <Parameter Type="System.String" Name="action" />
            </Instance>
        </Message>
        <Message Id="IllegalCabbingThreadCount" Number="218" SourceLineNumbers="no">
            <Instance>
                Illegal number of threads to create cabinets: '{0}' for -ct &lt;N&gt; command line option. Specify the number of threads to use like -ct 2.
                <Parameter Type="System.String" Name="numThreads" />
            </Instance>
        </Message>
        <Message Id="IllegalEnvironmentVariable" Number="219" SourceLineNumbers="no">
            <Instance>
                The {0} environment variable is set to an invalid value of '{1}'.
                <Parameter Type="System.String" Name="environmentVariable" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="InvalidKeyColumn" Number="220" SourceLineNumbers="no">
            <Instance>
                The definition for the '{0}' table's '{1}' column is an invalid foreign key relationship to the {2} table's column number {3}.  It is not a valid foreign key table column number because it is too small (less than 1) or greater than the count of columns in the foreign table's definition.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="columnName" />
                <Parameter Type="System.String" Name="foreignTableName" />
                <Parameter Type="System.Int32" Name="foreignColumnNumber" />
            </Instance>
        </Message>
        <Message Id="CollidingModularizationTypes" Number="221" SourceLineNumbers="no">
            <Instance>
                The definition for the '{0}' table's '{1}' column is a foreign key relationship to the '{2}' table's column number {3}.  The modularization types of the two column definitions differ: one is {4} and the other is {5}.  Change one of the modularization types so that they match.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="columnName" />
                <Parameter Type="System.String" Name="foreignTableName" />
                <Parameter Type="System.Int32" Name="foreignColumnNumber" />
                <Parameter Type="System.String" Name="modularizationType" />
                <Parameter Type="System.String" Name="foreignModularizationType" />
            </Instance>
        </Message>
        <Message Id="CubeFileNotFound" Number="222" SourceLineNumbers="no">
            <Instance>
                The cube file '{0}' cannot be found.  This file is required for MSI validation.
                <Parameter Type="System.String" Name="cubeFile" />
            </Instance>
        </Message>
        <Message Id="OpenDatabaseFailed" Number="223" SourceLineNumbers="no">
            <Instance>
                Failed to open database '{0}'.  Ensure it is a valid database, and it is not open by another process.
                <Parameter Type="System.String" Name="databaseFile" />
            </Instance>
        </Message>
        <Message Id="OutputTypeMismatch" Number="224">
            <Instance>
                The types of the outputs do not match.  One output's type is '{0}' while the other is '{1}'.
                <Parameter Type="System.String" Name="beforeOutputType" />
                <Parameter Type="System.String" Name="afterOutputType" />
            </Instance>
        </Message>
        <Message Id="RealTableMissingPrimaryKeyColumn" Number="225">
            <Instance>
                The table '{0}' does not contain any primary key columns.  At least one column must be marked as the primary key to ensure this table can be patched.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="IllegalColumnName" Number="226">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a legal column name.  It will collide with the sentinel values used in the _TransformView table.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="NoDifferencesInTransform" Number="227">
            <Instance>
                The transform being built did not contain any differences so it could not be created.
            </Instance>
        </Message>
        <Message Id="OutputCodepageMismatch" Number="228">
            <Instance>
                The code pages of the outputs do not match.  One output's code page is '{0}' while the other is '{1}'.
                <Parameter Type="System.Int32" Name="beforeCodepage" />
                <Parameter Type="System.Int32" Name="afterCodepage" />
            </Instance>
        </Message>
        <Message Id="OutputCodepageMismatch2" Number="229">
            <Instance>
                The location of the mismatched code page related to the previous warning.
            </Instance>
        </Message>
        <Message Id="IllegalComponentWithAutoGeneratedGuid" Number="230">
            <Instance>
                The Component/@Guid attribute's value '*' is not valid for this component because it does not meet the criteria for having an automatically generated guid. Components using a Directory as a KeyPath or containing ODBCDataSource child elements cannot use an automatically generated guid. Make sure your component doesn't have a Directory as the KeyPath and move any ODBCDataSource child elements to components with explicit component guids.
            </Instance>
            <Instance>
                The Component/@Guid attribute's value '*' is not valid for this component because it does not meet the criteria for having an automatically generated guid. Components with registry keypaths and files cannot use an automatically generated guid. Create multiple components, each with one file and/or one registry value keypath, to use automatically generated guids.
                <Parameter Type="System.Boolean" Name="registryKeyPath" />
            </Instance>
        </Message>
      <Message Id="IllegalPathForGeneratedComponentGuid" Number="231">
            <Instance>
                The component '{0}' has a key file with path '{1}'.  Since this path is not rooted in one of the standard directories (like ProgramFilesFolder), this component does not fit the criteria for having an automatically generated guid.  (This error may also occur if a path contains a likely standard directory such as nesting a directory with name "Common Files" under ProgramFilesFolder.)
                <Parameter Type="System.String" Name="componentName" />
                <Parameter Type="System.String" Name="keyFilePath" />
            </Instance>
        </Message>
        <Message Id="IllegalTerminalServerCustomActionAttributes" Number="232">
            <Instance>
                The CustomAction/@TerminalServerAware attribute's value is 'yes' but the Execute attribute is not 'deferred,' 'rollback,' or 'commit.' Terminal-Server-aware custom actions must be deferred, rollback, or commit custom actions. For more information, see http://msdn.microsoft.com/library/aa372071.aspx."
            </Instance>
        </Message>
        <Message Id="IllegalPropertyCustomActionAttributes" Number="233">
            <Instance>
                The CustomAction sets a property but its Execute attribute is not 'immediate' (the default). Property-setting custom actions cannot be deferred."
            </Instance>
        </Message>
        <Message Id="InvalidPreprocessorFunction" Number="234">
            <Instance>
                Ill-formed preprocessor function '${0}'.  Functions must have a prefix (like 'fun.'), a name at least 1 character long, and matching opening and closing parentheses.
                <Parameter Type="System.String" Name="variable" />
            </Instance>
        </Message>
        <Message Id="UndefinedPreprocessorFunction" Number="235">
            <Instance>
                Undefined preprocessor function '$({0})'.
                <Parameter Type="System.String" Name="variableName" />
            </Instance>
        </Message>
        <Message Id="PreprocessorExtensionEvaluateFunctionFailed" Number="236">
            <Instance>
                In the preprocessor extension that handles prefix '{0}' while trying to call function '{1}({2})' and exception has occurred : {3}
                <Parameter Type="System.String" Name="prefix" />
                <Parameter Type="System.String" Name="function" />
                <Parameter Type="System.String" Name="args" />
                <Parameter Type="System.String" Name="message" />
            </Instance>
        </Message>
        <Message Id="PreprocessorExtensionGetVariableValueFailed" Number="237">
            <Instance>
                In the preprocessor extension that handles prefix '{0}' while trying to get the value for variable '{1}' and exception has occured : {2}
                <Parameter Type="System.String" Name="prefix" />
                <Parameter Type="System.String" Name="variable" />
                <Parameter Type="System.String" Name="message" />
            </Instance>
        </Message>
        <Message Id="InvalidManifestContent" Number="238">
            <Instance>
                The manifest '{0}' does not have the required assembly/assemblyIdentity element.
                <Parameter Type="System.String" Name="fileName" />
            </Instance>
        </Message>
        <Message Id="InvalidWixTransform" Number="239" SourceLineNumbers="no">
            <Instance>
                The file '{0}' is not a valid Windows Installer XML Transform.
                <Parameter Type="System.String" Name="fileName" />
            </Instance>
        </Message>
        <Message Id="UnexpectedFileExtension" Number="240" SourceLineNumbers="no">
            <Instance>
                The file '{0}' has an unexpected extension. Expected one of the following: '{1}'.
                <Parameter Type="System.String" Name="fileName" />
                <Parameter Type="System.String" Name="expectedExtensions" />
            </Instance>
        </Message>
        <Message Id="UnexpectedTableInPatch" Number="241">
            <Instance>
                An unexpected row in the '{0}' table was found in this patch.  Patches cannot contain the '{0}' table.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="InvalidProductVersion" Number="242">
            <Instance>
                Invalid product version '{0}'. Product version must have a major version less than 256, a minor version less than 256, and a build version less than 65536.
                <Parameter Type="System.String" Name="version" />
            </Instance>
            <Instance>
                Invalid product version '{0}' in package '{1}'. When included in a bundle, all product version fields in an MSI package must be less than 65536.
                <Parameter Type="System.String" Name="version" />
                <Parameter Type="System.String" Name="packagePath" />
            </Instance>
        </Message>
        <Message Id="InvalidKeypathChange" Number="243">
            <Instance>
                Component '{0}' has a changed keypath in the transform '{1}'. Patches cannot change the keypath of a component.
                <Parameter Type="System.String" Name="component" />
                <Parameter Type="System.String" Name="transformPath" />
            </Instance>
        </Message>
        <Message Id="MissingValidatorExtension" Number="244" SourceLineNumbers="no">
            <Instance>
                The validator requires at least one extension. Add "ValidatorExtension, Wix" for the default implementation.
            </Instance>
        </Message>
        <Message Id="InvalidValidatorMessageType" Number="245" SourceLineNumbers="no">
            <Instance>
                Unknown validation message type '{0}'.
                <Parameter Type="System.String" Name="type" />
            </Instance>
        </Message>
        <Message Id="PatchWithoutTransforms" Number="246" SourceLineNumbers="no">
            <Instance>
                No transforms were provided to attach to the patch.
            </Instance>
        </Message>
        <Message Id="SingleExtensionSupported" Number="247" SourceLineNumbers="no">
            <Instance>
                Multiple extensions were specified on the command line, only a single extension is supported.
            </Instance>
        </Message>
        <Message Id="DuplicateTransform" Number="248" SourceLineNumbers="no">
            <Instance>
                The transform {0} was included twice on the command line. Each transform can be applied to a patch only once.
                <Parameter Type="System.String" Name="transform" />
            </Instance>
        </Message>
        <Message Id="BaselineRequired" Number="249" SourceLineNumbers="no">
            <Instance>
                No baseline was specified for one of the transforms specified. A baseline is required for all transforms in a patch.
            </Instance>
        </Message>
        <Message Id="PreprocessorError" Number="250">
            <Instance>
                {0}
                <Parameter Type="System.String" Name="message" />
            </Instance>
        </Message>
        <Message Id="ExpectedArgument" Number="251" SourceLineNumbers="no">
            <Instance>
                {0} is expected to be followed by a value argument.
                <Parameter Type="System.String" Name="argument" />
            </Instance>
        </Message>
        <Message Id="PatchWithoutValidTransforms" Number="252" SourceLineNumbers="no">
            <Instance>
                No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade.
            </Instance>
        </Message>
        <Message Id="ExpectedDecompiler" Number="253" SourceLineNumbers="no">
            <Instance>
                No decompiler was provided. {0} requires a decompiler.
                <Parameter Type="System.String" Name="identifier" />
            </Instance>
        </Message>
        <Message Id="ExpectedTableInMergeModule" Number="254" SourceLineNumbers="no">
            <Instance>
                The table '{0}' was expected but was missing.
                <Parameter Type="System.String" Name="identifier" />
            </Instance>
        </Message>
        <Message Id="UnexpectedElementWithAttributeValue" Number="255">
            <Instance>
                The {0} element cannot have a child element '{1}' unless attribute '{2}' is set to '{3}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="childElementName" />
                <Parameter Type="System.String" Name="attribute" />
                <Parameter Type="System.String" Name="attributeValue" />
            </Instance>
            <Instance>
                The {0} element cannot have a child element '{1}' unless attribute '{2}' is set to '{3}' or '{4}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="childElementName" />
                <Parameter Type="System.String" Name="attribute" />
                <Parameter Type="System.String" Name="attributeValue1" />
                <Parameter Type="System.String" Name="attributeValue2" />
            </Instance>
        </Message>
        <Message Id="ExpectedPatchIdInWixMsp" Number="256" SourceLineNumbers="no">
            <Instance>
                The WixMsp is missing the patch ID.
            </Instance>
        </Message>
        <Message Id="ExpectedMediaRowsInWixMsp" Number="257" SourceLineNumbers="no">
            <Instance>
                The WixMsp has no media rows defined.
            </Instance>
        </Message>
        <Message Id="WixFileNotFound" Number="258" SourceLineNumbers="no">
            <Instance>
                The file '{0}' cannot be found.
                <Parameter Type="System.String" Name="file" />
            </Instance>
        </Message>
        <Message Id="ExpectedClientPatchIdInWixMsp" Number="259" SourceLineNumbers="no">
            <Instance>
                The WixMsp is missing the client patch ID. Recompile the patch source files with the latest Windows Installer XML toolset.
            </Instance>
        </Message>
        <Message Id="NewRowAddedInTable" Number="260">
            <Instance>
                Product '{0}': Table '{1}' has a new row '{2}' added. This makes the patch not uninstallable.
                <Parameter Type="System.String" Name="productCode" />
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="rowId" />
            </Instance>
        </Message>
        <Message Id="PatchNotRemovable" Number="261" SourceLineNumbers="no">
            <Instance>
                This patch is not uninstallable. The 'Patch' element's attribute 'AllowRemoval' should be set to 'no'.
            </Instance>
        </Message>
        <Message Id="PathTooLong" Number="262">
            <Instance>
                '{0}' is too long, the fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
                <Parameter Type="System.String" Name="fileName" />
            </Instance>
        </Message>
        <Message Id="FileTooLarge" Number="263">
            <Instance>
                '{0}' is too large, file size must be less than 2147483648.
                <Parameter Type="System.String" Name="fileName" />
            </Instance>
        </Message>
        <Message Id="InvalidPlatformParameter" Number="264" SourceLineNumbers="no">
            <Instance>
                The parameter '{0}' is missing or has an invalid value {1}.  Possible values are x86, x64, or ia64.
                <Parameter Type="System.String" Name="name" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="InvalidPlatformValue" Number="265">
            <Instance>
                The Platform attribute has an invalid value {0}.  Possible values are x86, x64, or ia64.
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="IllegalValidationArguments" Number="266" SourceLineNumbers="no">
            <Instance>
                You may only specify a single default type using -t or specify custom validation using -serr and -val.
            </Instance>
        </Message>
        <Message Id="OrphanedComponent" Number="267">
            <Instance>
                Found orphaned Component '{0}'.  If this is a Product, every Component must have at least one parent Feature.  To include a Component in a Module, you must include it directly as a Component element of the Module element or indirectly via ComponentRef, ComponentGroup, or ComponentGroupRef elements.
                <Parameter Type="System.String" Name="componentName" />
            </Instance>
        </Message>
        <Message Id="IllegalCommandlineArgumentCombination" Number="268" SourceLineNumbers="no">
            <Instance>
                '-{0}' cannot be specfied in combination with '-{1}'.
                <Parameter Type="System.String" Name="arg1" />
                <Parameter Type="System.String" Name="arg2" />
            </Instance>
        </Message>
        <Message Id="ProductCodeInvalidForTransform" Number="269">
            <Instance>
                The value '*' is not valid for the ProductCode when used in a transform or in a patch. Copy the ProductCode from your target product MSI into the Product/@Id attribute value for your product authoring.
            </Instance>
        </Message>
        <Message Id="InsertInvalidSequenceActionOrder" Number="270">
            <Instance>
                Invalid order of actions {1} and {2} in sequence table {0}. Action {3} must occur after {1} and before {2}, but {2} is currently sequenced after {1}. Please fix the ordering or explicitly supply a location for the action {3}.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionNameBefore" />
                <Parameter Type="System.String" Name="actionNameAfter" />
                <Parameter Type="System.String" Name="actionNameNew" />
            </Instance>
        </Message>
        <Message Id="InsertSequenceNoSpace" Number="271">
            <Instance>
                Not enough space exists to sequence action {3} in table {0}. It must be sequenced after {1} and before {2}, but those two actions are currently sequenced next to each other. Please move one of those actions to allow {3} to be inserted between them.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionNameBefore" />
                <Parameter Type="System.String" Name="actionNameAfter" />
                <Parameter Type="System.String" Name="actionNameNew" />
            </Instance>
        </Message>
        <Message Id="MissingManifestForWin32Assembly" Number="272">
            <Instance>
                File '{0}' is marked as a Win32 assembly but it refers to assembly manifest '{1}' that is not present in this product.
                <Parameter Type="System.String" Name="file" />
                <Parameter Type="System.String" Name="manifest" />
            </Instance>
        </Message>
        <Message Id="UnableToOpenModule" Number="273">
            <Instance>
                Unable to open merge module '{0}'. Check to make sure the module language is correct. '{1}'
                <Parameter Type="System.String" Name="modulePath" />
                <Parameter Type="System.String" Name="message" />
            </Instance>
        </Message>
        <Message Id="ExpectedAttributeWhenElementNotUnderElement" Number="274">
            <Instance>
                The '{0}/@{1}' attribute was not found; it is required when element '{0}' is not nested under a '{2}' element.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="parentElementName" />
            </Instance>
        </Message>
        <Message Id="IllegalIdentifierLooksLikeFormatted" Number="275">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a legal identifier. The {0}/@{1} attribute does not support formatted string values, such as property names enclosed in brackets ([LIKETHIS]). The value must be the identifier of another element, such as the Directory/@Id attribute value.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="IllegalCodepageAttribute" Number="276">
            <Instance>
                The code page '{0}' is not a valid Windows code page. Please check the {1}/@{2} attribute value in your source file.
                <Parameter Type="System.String" Name="codepage" />
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="IllegalCompressionLevel" Number="277" SourceLineNumbers="no">
            <Instance>
                The compression level '{0}' is not valid. Valid values are 'none', 'low', 'medium', 'high', and 'mszip'.
                <Parameter Type="System.String" Name="compressionLevel" />
            </Instance>
        </Message>
        <Message Id="TransformSchemaMismatch" Number="278" SourceLineNumbers="no">
            <Instance>The transform schema does not match the database schema. The transform may have been generated from a different database.</Instance>
        </Message>
        <Message Id="DatabaseSchemaMismatch" Number="279">
            <Instance>
                The table definition of '{0}' in the target database does not match the table definition in the updated database. A transform requires that the target database schema match the updated database schema.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="ExpectedDirectoryGotFile" Number="280" SourceLineNumbers="no">
            <Instance>
                The {0} option requires a directory, but the provided path is a file: {1}
                <Parameter Type="System.String" Name="option" />
                <Parameter Type="System.String" Name="path" />
            </Instance>
        </Message>
        <Message Id="ExpectedFileGotDirectory" Number="281" SourceLineNumbers="no">
            <Instance>
                The {0} option requires a file, but the provided path is a directory: {1}
                <Parameter Type="System.String" Name="option" />
                <Parameter Type="System.String" Name="path" />
            </Instance>
        </Message>
        <Message Id="GacAssemblyNoStrongName" Number="282">
            <Instance>
                Assembly {0} in component {1} has no strong name and has been marked to be placed in the GAC. All assemblies installed to the GAC must have a valid strong name.
                <Parameter Type="System.String" Name="assemblyName" />
                <Parameter Type="System.String" Name="componentName" />
            </Instance>
        </Message>
        <Message Id="FileWriteError" Number="283" SourceLineNumbers="no">
            <Instance>
                Error writing to the path: '{0}'. Error message: '{1}'
                <Parameter Type="System.String" Name="path" />
                <Parameter Type="System.String" Name="error" />
            </Instance>
        </Message>
        <Message Id="InvalidCommandLineFileName" Number="284" SourceLineNumbers="no">
            <Instance>
                Invalid file name specified on the command line: '{0}'. Error message: '{1}'
                <Parameter Type="System.String" Name="fileName" />
                <Parameter Type="System.String" Name="error" />
            </Instance>
        </Message>
        <Message Id="ExpectedParentWithAttribute" Number="285">
            <Instance>
                When the {0}/@{1} attribute is specified, the {0} element must be nested under a {2} element.
                <Parameter Type="System.String" Name="parentElement" />
                <Parameter Type="System.String" Name="attribute" />
                <Parameter Type="System.String" Name="grandparentElement" />
            </Instance>
        </Message>
        <Message Id="IllegalWarningIdAsError" Number="286" SourceLineNumbers="no">
            <Instance>
                Illegal value '{0}' for the -wx&lt;N&gt; command line option. Specify a particular warning number, like '-wx6' to display the warning with ID 6 as an error, or '-wx' alone to suppress all warnings.
                <Parameter Type="System.String" Name="warningId" />
            </Instance>
        </Message>
        <Message Id="ExpectedAttributeOrElement" Number="287">
            <Instance>
                Element '{0}' missing attribute '{1}' or child element '{2}'. Exactly one of those is required.
                <Parameter Type="System.String" Name="parentElement" />
                <Parameter Type="System.String" Name="attribute" />
                <Parameter Type="System.String" Name="childElement" />
            </Instance>
        </Message>
        <Message Id="DuplicateVariableDefinition" Number="288" SourceLineNumbers="no">
            <Instance>
                The variable '{0}' with value '{1}' was previously declared with value '{2}'.
                <Parameter Type="System.String" Name="variableName" />
                <Parameter Type="System.String" Name="variableValue" />
                <Parameter Type="System.String" Name="variableCollidingValue" />
            </Instance>
        </Message>
        <Message Id="InvalidVariableDefinition" Number="289" SourceLineNumbers="no">
            <Instance>
                The variable definition '{0}' is not valid.  Variable definitions should be in the form -dname=value where the value is optional.
                <Parameter Type="System.String" Name="variableDefinition" />
            </Instance>
        </Message>
        <Message Id="DuplicateCabinetName" Number="290">
            <Instance>
                Duplicate cabinet name '{0}' found.
                <Parameter Type="System.String" Name="cabinetName" />
            </Instance>
        </Message>
        <Message Id="DuplicateCabinetName2" Number="291">
            <Instance>
                Duplicate cabinet name '{0}' error related to previous error.
                <Parameter Type="System.String" Name="cabinetName" />
            </Instance>
        </Message>
        <Message Id="InvalidAddedFileRowWithoutSequence" Number="292">
            <Instance>
                A row has been added to the File table with id '{1}' that does not have a sequence number assigned to it. Create your transform from a pair of msi's instead of xml outputs to get sequences assigned to your File table's rows.
                <Parameter Type="System.String" Name="fileRowId" />
            </Instance>
        </Message>
        <Message Id="DuplicateFileId" Number="293" SourceLineNumbers="no">
            <Instance>
                Multiple files with ID '{0}' exist. Windows Installer does not support file IDs that differ only by case. Change the file IDs to be unique.
                <Parameter Type="System.String" Name="fileId" />
            </Instance>
        </Message>
        <Message Id="FullTempDirectory" Number="294" SourceLineNumbers="no">
            <Instance>
                Unable to create temporary file. A common cause is that too many files that have names beginning with '{0}' are present. Delete any unneeded files in the '{1}' directory and try again.
                <Parameter Type="System.String" Name="prefix" />
                <Parameter Type="System.String" Name="directory" />
            </Instance>
        </Message>
        <Message Id="CreateCabAddFileFailed" Number="296" SourceLineNumbers="no">
            <Instance>
                An error (E_FAIL) was returned while adding files to a CAB file. This most commonly happens when creating a CAB file 2 GB or larger. Either reduce the size of your installation package, raise Media/@CompressionLevel to a higher compression level, or split your installation package's files into more than one CAB file.
            </Instance>
        </Message>
        <Message Id="CreateCabInsufficientDiskSpace" Number="297" SourceLineNumbers="no">
            <Instance>
                An error (ERROR_DISK_FULL) was returned while creating a CAB file. This means you have insufficient disk space - please clear more disk space and try this operation again.
            </Instance>
        </Message>
        <Message Id="UnresolvedBindReference" Number="298" SourceLineNumbers="yes">
            <Instance>
                Unresolved bind-time variable {0}.
                <Parameter Type="System.String" Name="BindRef" />
            </Instance>
        </Message>
        <Message Id="GACAssemblyIdentityWarning" Number="299" SourceLineNumbers="yes">
            <Instance>
                The destination name of file '{0}' does not match its assembly name '{1}' in your authoring. This will cause an installation failure for this assembly, because it will be installed to the Global Assembly Cache. To fix this error, update File/@Name of file '{0}' to be the actual name of the assembly.
                <Parameter Type="System.String" Name="fileName" />
                <Parameter Type="System.String" Name="assemblyName" />
            </Instance>
        </Message>
        <Message Id="IllegalCharactersInPath" Number="300" SourceLineNumbers="no">
            <Instance>
                Illegal characters in path '{0}'. Ensure you provided a valid path to the file.
                <Parameter Type="System.String" Name="pathName" />
            </Instance>
        </Message>
        <Message Id="ValidationFailedToOpenDatabase" Number="301" SourceLineNumbers="no">
            <Instance>
                Failed to open the database. During validation, this most commonly happens when attempting to open a database using an unsupported code page or a file that is not a valid Windows Installer database. Please use a different code page in Module/@Codepage, Package/@SummaryCodepage, Product/@Codepage, or WixLocalization/@Codepage; or make sure you provide the path to a valid Windows Installer database.
            </Instance>
        </Message>
        <Message Id="MustSpecifyOutputWithMoreThanOneInput" Number="302" SourceLineNumbers="no">
            <Instance>
                You must specify an output file using the "-o" or "-out" switch when you provide more than one input file.
            </Instance>
        </Message>
        <Message Id="IllegalSearchIdForParentDepth" Number="303">
            <Instance>
                When the parent DirectorySearch/@Depth attribute is greater than 1 for the DirectorySearch '{1}', the FileSearch/@Id attribute must be absent for FileSearch '{0}' unless the parent DirectorySearch/@AssignToProperty attribute value is 'yes'. Remove the FileSearch/@Id attribute for '{0}' to resolve this issue.
                <Parameter Type="System.String" Name="id" />
                <Parameter Type="System.String" Name="parentId" />
            </Instance>
        </Message>
        <Message Id="IdentifierTooLongError" Number="304">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is too long.  {0}/@{1} attribute's must be {3} characters long or less.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.Int32" Name="maxLength" />
            </Instance>
        </Message>
        <Message Id="InvalidRemoveComponent" Number="305">
            <Instance>
                Removing component '{0}' from feature '{1}' is not supported. Either the component was removed or the guid changed in the transform '{2}'. Add the component back, undo the change to the component guid, or remove the entire feature.
                <Parameter Type="System.String" Name="component" />
                <Parameter Type="System.String" Name="feature" />
                <Parameter Type="System.String" Name="transformPath" />
            </Instance>
        </Message>
        <Message Id="FinishCabFailed" Number="306" SourceLineNumbers="no">
            <Instance>
                An error (E_FAIL) was returned while finalizing a CAB file. This most commonly happens when creating a CAB file with more than 65535 files in it. Either reduce the number of files in your installation package or split your installation package's files into more than one CAB file using the Media element.
            </Instance>
        </Message>
        <Message Id="InvalidExtensionType" Number="307" SourceLineNumbers="no">
            <Instance>
                Either '{1}' was not defined in the assembly or the type defined in extension '{0}' could not be loaded.
                <Parameter Type="System.String" Name="extension" />
                <Parameter Type="System.String" Name="attributeType" />
            </Instance>
            <Instance>
                The extension type '{1}' in extension '{0}' does not inherit from the expected class '{2}'.
                <Parameter Type="System.String" Name="extension" />
                <Parameter Type="System.String" Name="className" />
                <Parameter Type="System.String" Name="expectedType" />
            </Instance>
            <Instance>
                The type '{1}' in extension '{0}' could not be loaded. Exception type '{2}' returned the following message: {3}
                <Parameter Type="System.String" Name="extension" />
                <Parameter Type="System.String" Name="className" />
                <Parameter Type="System.String" Name="exceptionType" />
                <Parameter Type="System.String" Name="exceptionMessage"/>
            </Instance>
        </Message>
        <Message Id="UseFipsArgument" Number="308" SourceLineNumbers="no">
            <Instance>
                The Federal Information Processing Standard (FIPS) appears to be enabled on the machine. You must either disable FIPS or use FIPS-compliant security algorithms to generate IDs by passing the -fips command-line switch or by setting &lt;FipsCompliant&gt;true&lt;/FipsCompliant&gt; in your .wixproj project.
            </Instance>
        </Message>
        <Message Id="ValidationFailedDueToMultilanguageMergeModule" Number="309" SourceLineNumbers="no">
            <Instance>
                Failed to open merge module for validation. The most common cause of this error is specifying that the merge module supports multiple languages (using the Package/@Languages attribute) but not including language-specific embedded transforms. To fix this error, make the merge module language-neutral, make it language-specific, embed language transforms as specified in the MSI SDK at http://msdn.microsoft.com/library/aa367799.aspx, or disable validation.
            </Instance>
        </Message>
        <Message Id="ValidationFailedDueToInvalidPackage" Number="310" SourceLineNumbers="no">
            <Instance>
                Failed to open package for validation. The most common cause of this error is validating an x64 package on an x86 system. To fix this error, run validation on an x64 system or disable validation.
            </Instance>
        </Message>
        <Message Id="InvalidStringForCodepage" Number="311">
            <Instance>
                A string was provided with characters that are not available in the specified database code page '{0}'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage.
                <Parameter Type="System.String" Name="codepage" />
            </Instance>
        </Message>
        <Message Id="InvalidEmbeddedUIFileName" Number="312">
            <Instance>
                The EmbeddedUI/@Name attribute value, '{0}', does not contain an extension. Windows Installer will not load an embedded UI DLL without an extension. Include an extension or just omit the Name attribute so it defaults to the file name portion of the Source attribute value.
                <Parameter Type="System.String" Name="codepage" />
            </Instance>
        </Message>
        <Message Id="UniqueFileSearchIdRequired" Number="313">
            <Instance>
                The DirectorySearch element '{0}' requires that the child {1} element has a unique Id when the DirectorySearch/@AssignToProperty attribute is set to 'yes'.
                <Parameter Type="System.String" Name="id" />
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeValueWhenNested" Number="314">
            <Instance>
                The {0}/@{1} attribute value, '{2}', cannot be specified when the {0} element is nested underneath a {3} element.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attrivuteValue" />
                <Parameter Type="System.String" Name="parentElementName" />
            </Instance>
        </Message>
        <Message Id="AdminImageRequired" Number="315" SourceLineNumbers="no">
            <Instance>
                Source information is required for the product '{0}'. If you ran torch.exe with both target and updated .msi files, you must first perform an administrative installation of both .msi files then pass -a when running torch.exe.
                <Parameter Type="System.String" Name="productCode" />
            </Instance>
        </Message>
        <Message Id="SamePatchBaselineId" Number="316">
            <Instance>
                The PatchBaseline/@Id attribute value '{0}' is a child of multiple Media elements. This prevents transforms from being resolved to distinct media. Change the PatchBaseline/@Id attribute values to be unique.
                <Parameter Type="System.String" Name="id" />
            </Instance>
        </Message>
        <Message Id="SameFileIdDifferentSource" Number="317">
            <Instance>
                Two different source paths '{1}' and '{2}' were detected for the same file identifier '{0}'. You must either author these under Media elements with different Id attribute values or in different patches.
                <Parameter Type="System.String" Name="fileId" />
                <Parameter Type="System.String" Name="sourcePath1" />
                <Parameter Type="System.String" Name="sourcePath2" />
            </Instance>
        </Message>
        <Message Id="HarvestSourceNotSpecified" Number="318" SourceLineNumbers="no">
            <Instance>
                A harvest source must be specified after the harvest type and can be followed by harvester arguments.
            </Instance>
        </Message>
        <Message Id="OutputTargetNotSpecified" Number="319" SourceLineNumbers="no">
            <Instance>
                The '-out' or '-o' parameter must specify a file path.
            </Instance>
        </Message>
        <Message Id="DuplicateCommandLineOptionInExtension" Number="320" SourceLineNumbers="no">
            <Instance>
                The command line option '{0}' has already been loaded by another Heat extension.
                <Parameter Type="System.String" Name="switch" />
            </Instance>
        </Message>
        <Message Id="HarvestTypeNotFound" Number="321" SourceLineNumbers="no">
            <Instance>
                The harvest type was not found in the list of loaded Heat extensions.
            </Instance>
            <Instance>
                The harvest type '{0}' was specified. Harvest types cannot start with a '-'. Remove the '-' to specify a valid harvest type.
                <Parameter Type="System.String" Name="harvestType" />
            </Instance>
        </Message>
        <Message Id="BothUpgradeCodesRequired" Number="322" SourceLineNumbers="no">
            <Instance>
                Both the target and updated product authoring must define the Product/@UpgradeCode attribute if the transform validates the UpgradeCode (default). Either define the Product/@UpgradeCode attribute in both the target and updated authoring, or set the Validate/@UpgradeCode attribute to 'no' in the patch authoring.
            </Instance>
        </Message>
        <Message Id="IllegalBinderClassName" Number="323" SourceLineNumbers="no">
            <Instance>
                Illegal binder class name specified for -binder command line option.
            </Instance>
        </Message>
        <Message Id="SpecifiedBinderNotFound" Number="324" SourceLineNumbers="no">
            <Instance>
                The specified binder class '{0}' was not found in any extensions.
                <Parameter Type="System.String" Name="binderClass" />
            </Instance>
        </Message>
        <Message Id="CannotLoadBinderFileManager" Number="325" SourceLineNumbers="no">
            <Instance>
                Cannot load binder file manager: {0}. Light can only load one binder file manager and has already loaded binder file manager: {1}.
                <Parameter Type="System.String" Name="binderFileManager" />
                <Parameter Type="System.String" Name="currentBinderFileManager" />
            </Instance>
        </Message>
        <Message Id="CannotLoadLinkerExtension" Number="326" SourceLineNumbers="no">
            <Instance>
                Cannot load linker extension: {0}. Light can only load one link extension and has already loaded link extension: {1}.
                <Parameter Type="System.String" Name="linkerExtension" />
                <Parameter Type="System.String" Name="currentLinkerExtension" />
            </Instance>
        </Message>
        <Message Id="UnableToGetAuthenticodeCertOfFile" Number="327" SourceLineNumbers="no">
            <Instance>
                Unable to get the authenticode certificate of '{0}'.  More information: {1}
                <Parameter Type="System.String" Name="filePath" />
                <Parameter Type="System.String" Name="moreInformation" />
            </Instance>
        </Message>
        <Message Id="UnableToGetAuthenticodeCertOfFileDownlevelOS" Number="328" SourceLineNumbers="no">
            <Instance>
                Unable to get the authenticode certificate of '{0}'. The cryptography API has limitations on Windows XP and Windows Server 2003.  More information: {1}
                <Parameter Type="System.String" Name="filePath" />
                <Parameter Type="System.String" Name="moreInformation" />
            </Instance>
        </Message>
        <Message Id="ReadOnlyOutputFile" Number="329" SourceLineNumbers="no">
            <Instance>
                Unable to output to file '{0}' because it is marked as read-only.
                <Parameter Type="System.String" Name="filePath" />
            </Instance>
        </Message>
        <Message Id="CannotDefaultComponentId" Number="330">
            <Instance>
                The Component/@Id attribute was not found; it is required when there is no valid keypath to use as the default id value.
            </Instance>
        </Message>
        <Message Id="ParentElementAttributeRequired" Number="331">
            <Instance>
                The parent {0} element is missing the {1} attribute that is required for the {2} child element.
                <Parameter Type="System.String" Name="parentElement" />
                <Parameter Type="System.String" Name="parentAttribute" />
                <Parameter Type="System.String" Name="childElement" />
            </Instance>
        </Message>
        <Message Id="PreprocessorExtensionPragmaFailed" Number="333">
            <Instance>
                Exception thrown while processing pragma '{0}'. The exception's message is: {1}
                <Parameter Type="System.String" Name="pragma" />
                <Parameter Type="System.String" Name="message" />
            </Instance>
        </Message>
        <Message Id="InvalidPreprocessorPragma" Number="334">
            <Instance>
                Malformed preprocessor pragma '{0}'. Pragmas must have a prefix, a name of at least 1 character long, and be followed by optional arguments.
                <Parameter Type="System.String" Name="variable" />
            </Instance>
        </Message>
        <Message Id="SmokeUnknownFileExtension" Number="335" SourceLineNumbers="no">
          <Instance>
            Unknown input file format - expected a .msi or .msm file.
          </Instance>
        </Message>
        <Message Id="SmokeUnsupportedFileExtension" Number="336" SourceLineNumbers="no">
          <Instance>
            Files with an extension of .msp are not currently supported.
          </Instance>
        </Message>
        <Message Id="SmokeMalformedPath" Number="337" SourceLineNumbers="no">
          <Instance>
            Path contains one or more invalid characters.
          </Instance>
        </Message>
        <Message Id="InvalidStubExe" Number="338" SourceLineNumbers="no">
            <Instance>
                Stub executable '{0}' is not a valid Win32 executable.
                <Parameter Type="System.String" Name="filename" />
            </Instance>
        </Message>
        <Message Id="StubMissingWixburnSection" Number="339" SourceLineNumbers="no">
            <Instance>
                Stub executable '{0}' does not contain a .wixburn data section.
                <Parameter Type="System.String" Name="filename" />
            </Instance>
        </Message>
        <Message Id="StubWixburnSectionTooSmall" Number="340" SourceLineNumbers="no">
            <Instance>
                Stub executable '{0}' .wixburn data section is too small to store the Burn container header.
                <Parameter Type="System.String" Name="filename" />
            </Instance>
        </Message>
        <Message Id="MissingBundleInformation" Number="341" SourceLineNumbers="no">
            <Instance>
                The Bundle is missing '{0}' data, and cannot continue.
                <Parameter Type="System.String" Name="data" />
            </Instance>
        </Message>
        <Message Id="UnexpectedGroupChild" Number="342" SourceLineNumbers="no">
            <Instance>
                A group parent ('{0}'/'{1}') had an unexpected child ('{2}'/'{3}').
                <Parameter Type="System.String" Name="parentType" />
                <Parameter Type="System.String" Name="parentId" />
                <Parameter Type="System.String" Name="childType" />
                <Parameter Type="System.String" Name="childId" />
            </Instance>
        </Message>
        <Message Id="OrderingReferenceLoopDetected" Number="343">
            <Instance>
                A circular reference of ordering dependencies was detected. The infinite loop includes: {0}. Ordering dependency references must form a directed acyclic graph.
                <Parameter Type="System.String" Name="loopList" />
            </Instance>
        </Message>
        <Message Id="IdentifierNotFound" Number="344" SourceLineNumbers="no">
            <Instance>
                An expected identifier ('{1}', of type '{0}') was not found.
                <Parameter Type="System.String" Name="type" />
                <Parameter Type="System.String" Name="identifier" />
            </Instance>
        </Message>
        <Message Id="MergePlatformMismatch" Number="345">
            <Instance>
                '{0}' is a 64-bit merge module but the product consuming it is 32-bit. 32-bit products can consume only 32-bit merge modules.
                <Parameter Type="System.String" Name="mergeModuleFile" />
            </Instance>
        </Message>
        <Message Id="IllegalRelativeLongFilename" Number="346">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a valid relative long name because it contains illegal characters.  Legal relative long names contain no more than 260 characters and must contain at least one non-period character.  Any character except for the follow may be used: ? | &gt; &lt; : / * ".
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeValueWithLegalList" Number="347">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not one of the legal options: {3}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="legalValueList" />
            </Instance>
        </Message>
        <Message Id="IllegalAttributeValueWithIllegalList" Number="348">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is one of the illegal options: {3}.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="illegalValueList" />
            </Instance>
        </Message>

        <Message Id="InvalidSummaryInfoCodePage" Number="349">
            <Instance>
                The code page '{0}' is invalid for summary information. You must specify an ANSI code page.
                <Parameter Type="System.Int32" Name="codePage" />
            </Instance>
        </Message>
        <Message Id="ValidationFailedDueToLowMsiEngine" Number="350" SourceLineNumbers="no">
            <Instance>
                The package being validated requires a higher version of Windows Installer than is installed on this machine. Validation cannot continue.
            </Instance>
        </Message>
        <Message Id="DuplicateSourcesForOutput" Number="351" SourceLineNumbers="no">
            <Instance>
                Multiple source files ({0}) have resulted in the same output file '{1}'.  This is likely because the source files only differ in extension or path.  Rename the source files to avoid this problem.
                <Parameter Type="System.String" Name="sourceList" />
                <Parameter Type="System.String" Name="outputFile" />
            </Instance>
        </Message>
        <Message Id="UnableToReadPackageInformation" Number="352">
            <Instance>
                Unable to read package '{0}'. {1}
                <Parameter Type="System.String" Name="packagePath" />
                <Parameter Type="System.String" Name="detailedErrorMessage" />
            </Instance>
        </Message>
        <Message Id="MultipleFilesMatchedWithOutputSpecification" Number="353" SourceLineNumbers="no">
            <Instance>
                A per-source file output specification has been provided ('{0}'), but multiple source files match the source specification ({1}).  Specifying a unique output requires that only a single source file match.
                <Parameter Type="System.String" Name="sourceSpecification" />
                <Parameter Type="System.String" Name="sourceList" />
            </Instance>
        </Message>
        <Message Id="InvalidBundle" Number="354" SourceLineNumbers="no">
          <Instance>
            Unable to read bundle executable '{0}'. This is not a valid WiX bundle.
            <Parameter Type="System.String" Name="bundleExecutable" />
          </Instance>
        </Message>
      <Message Id="BundleTooNew" Number="355" SourceLineNumbers="no">
        <Instance>
          Unable to read bundle executable '{0}', because this bundle was created with a newer version of WiX (bundle version '{1}'). You must use a newer version of Windows Installer XML in order to read this bundle.
          <Parameter Type="System.String" Name="bundleExecutable" />
          <!-- we use a 64-bit field here because the field is really a 32-bit UInt,
              but UInt gives a non-CLS-compliant warning.
              So 64-bit makes sure we don't drop the last bit -->
          <Parameter Type="System.Int64" Name="bundleVersion" />
        </Instance>
      </Message>
      <Message Id="WrongFileExtensionForNumberOfInputs" Number="356" SourceLineNumbers="no">
        <Instance>
          The extension '{0}' on the input specified '{1}' does not match the number of inputs required to handle an input with this extension. Check if you are missing an input or have too many.
          <Parameter Type="System.String" Name="inputExtension" />
          <Parameter Type="System.String" Name="input" />
        </Instance>
      </Message>
      <Message Id="MediaTableCollision" Number="357">
        <Instance>
          Only one of Media and MediaTemplate tables should be authored.
        </Instance>
      </Message>
      <Message Id="InvalidCabinetTemplate" Number="358">
        <Instance>
          CabinetTemplate attribute's value '{0}' must contain '{{0}}' and should contain no more than 8 characters followed by an optional extension of no more than 3 characters.  Any character except for the follow may be used: \ ? | &gt; &lt; : / * " + , ; = [ ] (space).  The Windows Installer team has recommended following the 8.3 format for external cabinet files and any other naming scheme is officially unsupported (which means it is not guaranteed to work on all platforms).
          <Parameter Type="System.String" Name="cabinetTemplate" />
        </Instance>
      </Message>
      <Message Id="MaximumUncompressedMediaSizeTooLarge" Number="359">
         <Instance>
          '{0}' is too large. Reduce the size of maximum uncompressed media size.
             <Parameter Type="System.Int32" Name="maximumUncompressedMediaSize" />
          </Instance>
      </Message>
      <Message Id="CatalogVerificationFailed" Number="360" SourceLineNumbers="no">
         <Instance>
          File '{0}' could not be verified with a catalog file.
             <Parameter Type="System.String" Name="fileName" />
         </Instance>
      </Message>
      <Message Id="CatalogFileHashFailed" Number="361" SourceLineNumbers="no">
         <Instance>
          Could not get hash of file '{0}'.  Error: {2}.
             <Parameter Type="System.String" Name="fileName" />
             <Parameter Type="System.Int32" Name="errorCode" />
         </Instance>
      </Message>
      <Message Id="ReservedNamespaceViolation" Number="362">
        <Instance>
          The {0}/@{1} attribute's value begins with the reserved prefix '{2}'. Some prefixes are reserved by the Windows Installer and WiX toolset for well-known values. Change your attribute's value to not begin with the same prefix.
          <Parameter Type="System.String" Name="element" />
          <Parameter Type="System.String" Name="attribute" />
          <Parameter Type="System.String" Name="prefix" />
        </Instance>
      </Message>
      <Message Id="PerUserButAllUsersEquals1" Number="363">
        <Instance>
          The MSI '{0}' is explicitly marked to not elevate so it must be a per-user package but the ALLUSERS Property is set to '1' creating a per-machine package. Remove the Property with Id='ALLUSERS' and use Package/@InstallScope attribute to be explicit instead.
          <Parameter Type="System.String" Name="path" />
        </Instance>
      </Message>
      <Message Id="UnsupportedAllUsersValue" Number="364">
        <Instance>
          The MSI '{0}' set the ALLUSERS Property to '{0}' which is not supported. Remove the Property with Id='ALLUSERS' and use Package/@InstallScope attribute instead.
          <Parameter Type="System.String" Name="path" />
          <Parameter Type="System.String" Name="value" />
        </Instance>
      </Message>
      <Message Id="MissingOrInvalidModuleInstallerVersion" Number="366">
        <Instance>
          The merge module '{0}' from file '{1}' is either missing or has an invalid installer version. The value read from the installer version in module's summary information was '{2}'. This should be a numeric value representing a valid installer version such as 200 or 301.
          <Parameter Type="System.String" Name="moduleId" />
          <Parameter Type="System.String" Name="mergeModuleFile" />
          <Parameter Type="System.String" Name="productInstallerVersion" />
        </Instance>
      </Message>
      <Message Id="IllegalGeneratedGuidComponentUnversionedKeypath" Number="367">
        <Instance>
          The Component/@Guid attribute's value '*' is not valid for this component because it does not meet the criteria for having an automatically generated guid. Components with more than one file cannot use an automatically generated guid unless a versioned file is the keypath and the other files are unversioned. This component's keypath is not versioned. Create multiple components to use automatically generated guids.
        </Instance>
      </Message>
      <Message Id="IllegalGeneratedGuidComponentVersionedNonkeypath" Number="368">
        <Instance>
          The Component/@Guid attribute's value '*' is not valid for this component because it does not meet the criteria for having an automatically generated guid. Components with more than one file cannot use an automatically generated guid unless a versioned file is the keypath and the other files are unversioned. This component has a non-keypath file that is versioned. Create multiple components to use automatically generated guids.
        </Instance>
      </Message>
      <Message Id="DuplicateComponentGuids" Number="369">
        <Instance>
          Component/@Id='{0}' has a @Guid value '{1}' that duplicates another component in this package. It is recommended to give each component its own unique GUID.
          <Parameter Type="System.String" Name="componentId" />
          <Parameter Type="System.String" Name="guid" />
        </Instance>
      </Message>
      <Message Id="DuplicateProviderDependencyKey" Number="370" SourceLineNumbers="no">
        <Instance>
          The provider dependency key '{0}' was already imported from the package with Id '{1}'. Please remove the Provides element with the key '{0}' from the package authoring.
          <Parameter Type="System.String" Name="providerKey" />
          <Parameter Type="System.String" Name="packageId" />
        </Instance>
      </Message>
      <Message Id="MissingDependencyVersion" Number="371" SourceLineNumbers="no">
        <Instance>
          The provider dependency version was not authored for the package with Id '{0}'. Please author the Provides/@Version attribute for this package.
          <Parameter Type="System.String" Name="packageId" />
        </Instance>
      </Message>

      <Message Id="UnexpectedElementWithAttribute" Number="372">
        <Instance>
          The {0} element cannot have a child element '{1}' when attribute '{2}' is set.
          <Parameter Type="System.String" Name="elementName" />
          <Parameter Type="System.String" Name="childElementName" />
          <Parameter Type="System.String" Name="attribute" />
        </Instance>
      </Message>
      <Message Id="ExpectedAttributeWithElement" Number="373">
        <Instance>
          The {0} element must have attribute '{1}' when child element '{2}' is present.
          <Parameter Type="System.String" Name="elementName" />
          <Parameter Type="System.String" Name="attribute" />
          <Parameter Type="System.String" Name="childElementName" />
        </Instance>
      </Message>
      <Message Id="DuplicatedUiLocalization" Number="374">
        <Instance>
          The localization for control {0} in dialog {1} is duplicated. Only one localization per control is allowed.
          <Parameter Type="System.String" Name="controlName" />
          <Parameter Type="System.String" Name="dialogName" />
        </Instance>
        <Instance>
          The localization for dialog {0} is duplicated. Only one localization per dialog is allowed.
          <Parameter Type="System.String" Name="dialogName" />
        </Instance>
      </Message>
      <Message Id="MaximumCabinetSizeForLargeFileSplittingTooLarge" Number="375">
        <Instance>
            '{0}' is too large. Reduce the size of maximum cabinet size for large file splitting. The maximum permitted value is '{1}' MB.
            <Parameter Type="System.Int32" Name="maximumCabinetSizeForLargeFileSplitting" />
            <Parameter Type="System.Int32" Name="maxValueOfMaxCabSizeForLargeFileSplitting" />
        </Instance>
      </Message>
      <Message Id="SplitCabinetCopyRegistrationFailed" Number="376" SourceLineNumbers="no">
        <Instance>
          Failed to register the copy command for cabinet '{0}' formed by splitting cabinet '{1}'.
          <Parameter Type="System.String" Name="newCabName" />
          <Parameter Type="System.String" Name="firstCabName" />
        </Instance>
      </Message>
      <Message Id="SplitCabinetNameCollision" Number="377" SourceLineNumbers="no">
        <Instance>
          The cabinet name '{0}' collides with the new cabinet formed by splitting cabinet '{1}', consider renaming cabinet '{0}'.
          <Parameter Type="System.String" Name="newCabName" />
          <Parameter Type="System.String" Name="firstCabName" />
        </Instance>
      </Message>
      <Message Id="SplitCabinetInsertionFailed" Number="378" SourceLineNumbers="no">
        <Instance>
            Could not find the last split cabinet '{2}' in the Media Table. So failed to add new cabinet '{0}' formed by splitting cabinet '{1}' to the installer package.
            <Parameter Type="System.String" Name="newCabName" />
          <Parameter Type="System.String" Name="firstCabName" />
          <Parameter Type="System.String" Name="lastCabinetOfThisSequence" />
        </Instance>
      </Message>
      <Message Id="InvalidPreprocessorFunctionAutoVersion" Number="379">
        <Instance>
          Invalid AutoVersion template specified.
        </Instance>
      </Message>
      <Message Id="InvalidModuleOrBundleVersion" Number="380">
        <Instance>
          Invalid {0}/@Version '{1}'. {0} version has a max value of "65535.65535.65535.65535" and must be all numeric.
          <Parameter Type="System.String" Name="moduleOrBundle" />
          <Parameter Type="System.String" Name="version" />
        </Instance>
      </Message>
      <Message Id="UnsupportedPlatformForElement" Number="381">
        <Instance>
          The element {1} does not support platform '{0}'. Consider removing the element or using the preprocessor to conditionally include the element based on the platform.
          <Parameter Type="System.String" Name="platform" />
          <Parameter Type="System.String" Name="elementName" />
        </Instance>
      </Message>
      <Message Id="MissingMedia" Number="382">
        <Instance>
          There is no media defined for disk id '{0}'. You must author either &lt;Media Id='{0}' ...&gt; or &lt;MediaTemplate ...&gt;.
          <Parameter Type="System.Int32" Name="diskId" />
        </Instance>
      </Message>
      <Message Id="RemotePayloadUnsupported" Number="383">
        <Instance>
          The RemotePayload element can only be used for ExePackage and MsuPackage payloads.
        </Instance>
      </Message>
      <Message Id="IllegalYesNoAlwaysValue" Number="384">
          <Instance>
              The {0}/@{1} attribute's value, '{2}', is not a legal yes/no/always value.  The only legal values are 'always', 'no' or 'yes'.
              <Parameter Type="System.String" Name="elementName" />
              <Parameter Type="System.String" Name="attributeName" />
              <Parameter Type="System.String" Name="value" />
          </Instance>
      </Message>
      <Message Id="TooDeeplyIncluded" Number="385">
        <Instance>
          Include files cannot be nested more deeply than {0} times. Make sure included files don't accidentally include themselves.
          <Parameter Type="System.Int32" Name="depth" />
        </Instance>
      </Message>
      <Message Id="TooManyColumnsInRealTable" Number="386" SourceLineNumbers="no">
        <Instance>
          The table '{0}' contains {1} columns which is not supported by Windows Installer.  Windows Installer supports a maximum of {2} columns.
          <Parameter Type="System.String" Name="tableName" />
          <Parameter Type="System.Int32" Name="columnCount" />
          <Parameter Type="System.Int32" Name="supportedColumnCount" />
        </Instance>
      </Message>
      <Message Id="IncompatiblePackageElevationAttributes" Number="387">
          <Instance>
              The {0}/@{1} attribute's value, '{2}', is not compatible with attribute @{3}'s value, '{4}'. It is recommended that only the InstallScope attribute be used.
              <Parameter Type="System.String" Name="elementName" />
              <Parameter Type="System.String" Name="attribute1Name" />
              <Parameter Type="System.String" Name="attribute1Value" />
              <Parameter Type="System.String" Name="attribute2Name" />
              <Parameter Type="System.String" Name="attribute2Value" />
          </Instance>
      </Message>
      <Message Id="InsecureBundleFilename" Number="388" SourceLineNumbers="no">
        <Instance>
          The file name '{0}' creates an insecure bundle. Windows will load unnecessary compatibility shims into a bundle with that file name. These compatibility shims can be DLL hijacked allowing attackers to compromise your customers' computer. Choose a different bundle file name.
          <Parameter Type="System.String" Name="filename" />
        </Instance>
      </Message>
    </Class>

    <Class Name="WixWarnings" ContainerName="WixWarningEventArgs" BaseContainerName="MessageEventArgs" Level="Warning">
        <Message Id="IdentifierCannotBeModularized" Number="1000">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is {3} characters long.  It will be too long if modularized.  The identifier shouldn't be longer than {4} characters long to allow for modularization (appending a guid for merge modules).
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="identifier" />
                <Parameter Type="System.Int32" Name="length" />
                <Parameter Type="System.Int32" Name="maximumLength" />
            </Instance>
        </Message>
        <Message Id="EmptyAttributeValue" Number="1001">
            <Instance>
                The {0}/@{1} attribute's value cannot be an empty string.  If you want the value to be null or empty, simply remove the entire attribute.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="UnableToFindFileFromCabOrImage" Number="1002">
            <Instance>
                Unable to find existing file {0} to place in src location {1}.  Will likely cause a linker break.
                <Parameter Type="System.String" Name="existingFileSpec" />
                <Parameter Type="System.String" Name="srcFileSpec" />
            </Instance>
        </Message>
        <Message Id="CopyFileFileIdUseless" Number="1003">
            <Instance>Since the CopyFile/@FileId attribute was specified but none of the following attributes (DestinationName, DestinationDirectory, DestinationProperty) were specified, this authoring will not do anything.</Instance>
        </Message>
        <Message Id="NestedInstall" Number="1004">
            <Instance>
                The {0}.{1} column's value, '{2}', indicates a nested install.  Nested installations are not supported by the Windows Installer XML team.  This action will be left out of the decompiled output.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="columnName" />
                <Parameter Type="System.Object" Name="value" />
            </Instance>
        </Message>
        <Message Id="OrphanedProgId" Number="1005">
            <Instance>
                ProgId '{0}' is orphaned.  It has no associated component, so it will never install.  Every ProgId should have either a parent Class element or child Extension element (at any distance).
                <Parameter Type="System.String" Name="progId" />
            </Instance>
        </Message>
        <Message Id="PropertyUseless" Number="1006">
            <Instance>
                Property '{0}' does not contain a Value attribute and is not marked as Admin, Secure, or Hidden.  The Property element is being ignored.
                <Parameter Type="System.String" Name="id" />
            </Instance>
        </Message>
        <Message Id="RemoveFileNameRequired" Number="1007">
            <Instance>The RemoveFile/@Name attribute will soon become required.  In order to match the old functionality of not specifying this attribute, please use the new RemoveFolder element instead.</Instance>
        </Message>
        <Message Id="SuppressAction" Number="1008">
            <Instance>
                The action '{0}' in the {1} table is being suppressed.
                <Parameter Type="System.String" Name="action" />
                <Parameter Type="System.String" Name="sequenceName" />
            </Instance>
        </Message>
        <Message Id="SuppressMergedAction" Number="1009" SourceLineNumbers="no">
            <Instance>
                The merged action '{0}' in the {1} table is being suppressed.
                <Parameter Type="System.String" Name="action" />
                <Parameter Type="System.String" Name="sequenceName" />
            </Instance>
        </Message>
        <Message Id="TargetDirCorrectedDefaultDir" Number="1010" SourceLineNumbers="no">
            <Instance>
                The Directory with Id 'TARGETDIR' must have the value 'SourceDir' in its 'DefaultDir' column. This has been automatically corrected for you in the decompiled output.
            </Instance>
        </Message>
        <Message Id="AccessDeniedForDeletion" Number="1011">
            <Instance>
                Access denied; cannot delete '{0}'.
                <Parameter Type="System.String" Name="tempFilesBasePath" />
            </Instance>
        </Message>
        <Message Id="DirectoryInUse" Number="1012">
            <Instance>
                The directory '{0}' is in use and cannot be deleted.
                <Parameter Type="System.String" Name="filePath" />
            </Instance>
        </Message>
        <Message Id="AccessDeniedForSettingAttributes" Number="1013">
            <Instance>
                Access denied; cannot set attributes on '{0}'.
                <Parameter Type="System.String" Name="filePath" />
            </Instance>
        </Message>
        <Message Id="UnknownAction" Number="1024">
            <Instance>
                The {0} table contains an action '{1}' which is not a known custom action, dialog, or standard action.  This action will be left out of the decompiled output.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName" />
            </Instance>
        </Message>
        <Message Id="IdentifierTooLong" Number="1026">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is too long for an identifier.  Standard identifiers are 72 characters long or less.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="UnknownPermission" Number="1030">
            <Instance>
                The {0} table contains a row with primary key '{1}' which has an unknown permission at bit {2}.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="primaryKey" />
                <Parameter Type="System.Int32" Name="bitPosition" />
            </Instance>
        </Message>
        <Message Id="DirectoryRedundantNames" Number="1031">
            <Instance>
                The {0} element's {1} and {2} values are both '{3}'.  This is redundant; the {2} attribute should be removed.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="shortNameAttributeName" />
                <Parameter Type="System.String" Name="longNameAttributeName" />
                <Parameter Type="System.String" Name="attributeValue" />
            </Instance>
            <Instance>
                The {0} element's source and destination names are identical.  This is redundant; the {1} and {2} attributes should be removed if present.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="sourceNameAttributeName" />
                <Parameter Type="System.String" Name="longSourceAttributeName" />
            </Instance>
        </Message>
        <Message Id="UnableToResetAcls" Number="1032" SourceLineNumbers="no">
            <Instance>Unable to reset acls on destination files.</Instance>
        </Message>
        <Message Id="MediaExternalCabinetFilenameIllegal" Number="1033">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is not a valid external cabinet name.  Legal cabinet names should follow 8.3 format: they should contain no more than 8 characters followed by an optional extension of no more than 3 characters.  Any character except for the following may be used: \ ? | &gt; &lt; : / * " + , ; = [ ] (space).  The Windows Installer team has recommended following the 8.3 format for external cabinet files and any other naming scheme is officially unsupported (which means it is not guaranteed to work on all platforms).
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="DeprecatedPreProcVariable" Number="1034">
            <Instance>
                The built-in preprocessor variable '{0}' is deprecated.  Please correct your authoring to use the new '{1}' preprocessor variable instead.
                <Parameter Type="System.String" Name="oldName" />
                <Parameter Type="System.String" Name="newName" />
            </Instance>
        </Message>
        <Message Id="FileSearchFileNameIssue" Number="1043">
            <Instance>
                The {0} element's {1} and {2} attributes were found.  Due to a bug with the Windows Installer, only the Name or LongName attribute should be used.  Use the Name attribute for 8.3 compliant file names and the LongName attribute for longer ones.  When using only the LongName attribute, ICE03 should be ignored for the Signature table's FileName column.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName1" />
                <Parameter Type="System.String" Name="attributeName2" />
            </Instance>
        </Message>
        <Message Id="AmbiguousFileOrDirectoryName" Number="1044">
            <Instance>
                The {0}/@{1} attribute's value '{2}' is an ambiguous short name because it ends with a '~' character followed by a number.  Under some circumstances, this name could resolve to more than one file or directory name and lead to unpredictable results (for example 'MICROS~1' may correspond to 'Microsoft Shared' or 'Microsoft Foo' or literally 'Micros~1').
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="IdenticalRowWarning" Number="1045">
            <Instance>
                The row with symbol: '{0}' is defined identically in another section.  See the next message for the identical row.
                <Parameter Type="System.String" Name="symbolName" />
            </Instance>
        </Message>
        <Message Id="IdenticalRowWarning2" Number="1046">
            <Instance>Location of row related to previous error.</Instance>
        </Message>
        <Message Id="UnresolvedReferenceWarning" Number="1047">
            <Instance>
                Unresolved reference to symbol '{2}' in section '{0}:{1}'.
                <Parameter Type="System.String" Name="sectionType" />
                <Parameter Type="System.String" Name="sectionId" />
                <Parameter Type="System.String" Name="referencedSymbol" />
            </Instance>
        </Message>
        <Message Id="PossiblyIncorrectTypelibVersion" Number="1048">
            <Instance>
                The Typelib table entry with Id '{0}' could have an incorrect version of '256.0'.  InstallShield has a bug relating to the Typelib Version column: it will incorrectly set the value '65536' in to represent version '1.0'.  However, this number actually corresponds to version '256.0'.  This bug will not affect the typelib version that is registered during installation, however, it will prevent the Windows Installer from correctly identifying whether a typelib is already installed and lead to unnecessary reinstallations of the typelib.
                <Parameter Type="System.String" Name="id" />
            </Instance>
        </Message>
        <Message Id="ImplicitComponentPrimaryFeature" Number="1049" SourceLineNumbers="no">
            <Instance>
                The component '{0}' does not have an explicit primary feature parent specified.  If the source files are linked in a different order, the primary parent feature may change.  To prevent accidental changes, the primary feature parent should be set to 'yes' in one of the ComponentRef/@Primary, ComponentGroupRef/@Primary, or FeatureGroupRef/@Primary locations for this component.
                <Parameter Type="System.String" Name="componentId" />
            </Instance>
        </Message>
        <Message Id="ActionSequenceCollision" Number="1050">
            <Instance>
                The {0} table contains actions '{1}' and '{2}' which both have the same sequence number {3}.  Please change the sequence number for one of these actions to avoid an ICE warning.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName1" />
                <Parameter Type="System.String" Name="actionName2" />
                <Parameter Type="System.Int32" Name="sequenceNumber" />
            </Instance>
        </Message>
        <Message Id="ActionSequenceCollision2" Number="1051">
            <Instance>The location of the action related to previous warning.</Instance>
        </Message>
        <Message Id="SuppressAction2" Number="1052">
            <Instance>The location of the suppressed action related to previous warning.</Instance>
        </Message>
        <Message Id="UnexpectedTableInProduct" Number="1053">
            <Instance>
                An unexpected row in the '{0}' table was found in this product.  Products should not contain the '{0}' table.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="DeprecatedAttribute" Number="1054">
            <Instance>
                The {0}/@{1} attribute has been deprecated.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute has been deprecated.  Please use the {2} attribute instead.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="newAttributeName" />
            </Instance>
            <Instance>
                The {0}/@{1} attribute has been deprecated.  Please use the {2} or {3} attribute instead.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="newAttributeName1" />
                <Parameter Type="System.String" Name="newAttributeName2" />
            </Instance>
        </Message>
        <Message Id="MergeRescheduledAction" Number="1055">
            <Instance>
                The {0} table contains an action '{1}' which cannot be merged from the merge module '{2}'.  This action is likely colliding with an action in the database that is being created.  The colliding action may have been authored in the database or merged in from another merge module.  If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module.  If this is a custom action, it should only be declared in the database or one merge module.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="actionName" />
                <Parameter Type="System.String" Name="mergeModuleFile" />
            </Instance>
        </Message>
        <Message Id="MergeTableFailed" Number="1056">
            <Instance>
                The {0} table contains a row with primary key(s) '{1}' which cannot be merged from the merge module '{2}'.  This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="primaryKeys" />
                <Parameter Type="System.String" Name="mergeModuleFile" />
            </Instance>
        </Message>
        <Message Id="DecompiledStandardActionRelativelyScheduledInModule" Number="1057">
            <Instance>
                The {0} table contains a standard action '{1}' that does not have a sequence number specified.  A value in the Sequence column is required for standard actions in a merge module.  Remove the action from the decompiled authoring to have Windows Installer XML automatically sequence it.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName" />
            </Instance>
        </Message>
        <Message Id="IllegalActionInSequence" Number="1058">
            <Instance>
                The {0} table contains an action '{1}' which is not allowed in this table.  If this is a standard action then it is not valid for this table, if it is a custom action or dialog then this table does not accept actions of that type.  This action will be left out of the decompiled output.
                <Parameter Type="System.String" Name="sequenceTableName" />
                <Parameter Type="System.String" Name="actionName" />
            </Instance>
        </Message>
        <Message Id="ExpectedForeignRow" Number="1059">
            <Instance>
                The {0} table contains a row with primary key(s) '{1}' whose {2} column contains a value, '{3}', which specifies a foreign key relationship with the {4} table.  However, since the expected foreign row specified by this value does not exist, this will result in some information being left out of the decompiled output.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="primaryKey" />
                <Parameter Type="System.String" Name="columnName" />
                <Parameter Type="System.String" Name="columnValue" />
                <Parameter Type="System.String" Name="foreignTableName" />
            </Instance>
            <Instance>
                The {0} table contains a row with primary key(s) '{1}' whose {2} and {4} columns contain the values, '{3}' and '{5}', which specify a foreign key relationship with the {6} table.  However, since the expected foreign row specified by this value does not exist, this will result in some information being left out of the decompiled output.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="primaryKey" />
                <Parameter Type="System.String" Name="columnName1" />
                <Parameter Type="System.String" Name="columnValue1" />
                <Parameter Type="System.String" Name="columnName2" />
                <Parameter Type="System.String" Name="columnValue2" />
                <Parameter Type="System.String" Name="foreignTableName" />
            </Instance>
        </Message>
        <Message Id="DecompilingAsCustomTable" Number="1060">
            <Instance>
                The {0} table is being decompiled as a custom table.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="IllegalPatchCreationTable" Number="1061">
            <Instance>
                The {0} table is not legal in a patch creation file.  The information in this table will be left out of the decompiled output.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="SkippingMergeModuleTable" Number="1062">
            <Instance>
                The {0} table can only be represented in Windows Installer XML for merge modules.  The information in this table will be left out of the decompiled output.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="SkippingPatchCreationTable" Number="1063">
            <Instance>
                The {0} table can only be represented in Windows Installer XML for patch creation files.  The information in this table will be left out of the decompiled output.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="UnrepresentableColumnValue" Number="1064">
            <Instance>
                The {0}.{1} column's value, '{2}', cannot currently be represented in the Windows Installer XML schema.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="columnName" />
                <Parameter Type="System.Object" Name="value" />
            </Instance>
        </Message>
        <Message Id="DeprecatedTable" Number="1065" SourceLineNumbers="no">
            <Instance>
                The {0} table is not supported by the Windows Installer XML toolset because it has been deprecated by the Windows Installer team.  Any information in this table will be left out of the decompiled output.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="PatchTable" Number="1066">
            <Instance>
                The {0} table is added to the install package by a transform from a patch package (.msp) and not authored directly into an install package (.msi). The information in this table will be left out of the decompiled output.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="IllegalColumnValue" Number="1067">
            <Instance>
                The {0}.{1} column's value, '{2}', is not a recognized legal value.  This information will be left out of the decompiled output.
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="columnName" />
                <Parameter Type="System.Object" Name="value" />
            </Instance>
        </Message>
        <Message Id="DeprecatedLongNameAttribute" Number="1069">
            <Instance>
                The {0}/@{1} attribute has been deprecated.  Since Windows Installer XML now has the ability to generate short file/directory names, the desired name should be specified in the {2} attribute instead.  If the name specified in the {2} attribute is a short name, then Windows Installer XML will not generate a short name.  If the name specified in the {2} attribute is a long name and you want to manually specify the short name, please set the short name value in the {3} attribute.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="longNameAttributeName" />
                <Parameter Type="System.String" Name="nameAttributeName" />
                <Parameter Type="System.String" Name="shortNameAttributeName" />
            </Instance>
        </Message>
        <Message Id="GeneratedShortFileNameConflict" Number="1070">
            <Instance>
                The short file name '{0}' was generated for multiple files that may be installed to the same directory.  This could be due to conflicting long file names specified by the File/@Name attribute.  If that is the case, please resolve the conflict in those attributes.  Otherwise, please manually set the File/@ShortName attribute on the conflicting row to fix the collision.  If one of the colliding files was added via a patch, that short file name should be specified manually to avoid disturbing the original short file name.
                <Parameter Type="System.String" Name="shortFileName" />
            </Instance>
        </Message>
        <Message Id="GeneratedShortFileNameConflict2" Number="1071">
            <Instance>
                The location of a conflicting generated short file name related to the previous warning.
            </Instance>
        </Message>
        <Message Id="DangerousTableInMergeModule" Number="1072">
            <Instance>
                Merge modules should not contain the '{0}' table because all merge conflicts cannot avoided.  However, this warning can be suppressed if all of the consumers of the Merge Module agree to not duplicate identifiers in the '{0}' table.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="DeprecatedLocalizationVariablePrefix" Number="1073">
            <Instance>
                The localization variable $(loc.{0}) uses a deprecated prefix '$'.  Please use the '!' prefix instead.  Since the prefix '$' is also used by the preprocessor, it has been deprecated to avoid namespace collisions.
                <Parameter Type="System.String" Name="variableId" />
            </Instance>
        </Message>
        <Message Id="PlaceholderValue" Number="1074">
            <Instance>
                The {0}/@{1} attribute's value, '{2}', is a placeholder value used in example files.  Please replace this placeholder with the appropriate value.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="MissingUpgradeCode" Number="1075">
            <Instance>The Product/@UpgradeCode attribute was not found; it is strongly recommended to ensure that this product can be upgraded.</Instance>
        </Message>
        <Message Id="ValidationWarning" Number="1076">
            <Instance>
                {0}: {1}
                <Parameter Type="System.String" Name="ice" />
                <Parameter Type="System.String" Name="message" />
            </Instance>
        </Message>
        <Message Id="PropertyValueContainsPropertyReference" Number="1077">
            <Instance>
                The '{0}' Property contains '[{1}]' in its value which is an illegal reference to another property.  If this value is a string literal, not a property reference, please ignore this warning.  To set a property with the value of another property, use a CustomAction with Property and Value attributes.
                <Parameter Type="System.String" Name="propertyId" />
                <Parameter Type="System.String" Name="otherProperty" />
            </Instance>
        </Message>
        <Message Id="DeprecatedUpgradeProperty" Number="1078">
            <Instance>Specifying a Property element as a child of an Upgrade element has been deprecated.  Please specify this Property element as a child of a different element such as Product or Fragment.</Instance>
        </Message>
        <Message Id="EmptyCabinet" Number="1079">
            <Instance>
                The cabinet '{0}' does not contain any files.  If this installation contains no files, this warning can likely be safely ignored.  Otherwise, please add files to the cabinet or remove it.
                <Parameter Type="System.String" Name="cabinetName" />
            </Instance>
            <Instance>
                The cabinet '{0}' does not contain any files.  If this patch contains no files, this warning can likely be safely ignored.  Otherwise, try passing -p to torch.exe when first building the transforms, or add a ComponentRef to your PatchFamily authoring to pull changed files into the cabinet.
                <Parameter Type="System.String" Name="cabinetName" />
                <Parameter Type="System.Boolean" Name="isPatch" />
            </Instance>
        </Message>
        <Message Id="DeprecatedRegistryElement" Number="1080">
            <Instance>The Registry element has been deprecated.  Please use one of the new elements which replaces its functionality: RegistryKey for creating registry keys, RegistryValue for writing registry values, RemoveRegistryKey for removing registry keys, and RemoveRegistryValue for removing registry values.</Instance>
        </Message>
        <Message Id="IllegalRegistryKeyPath" Number="1081">
            <Instance>
                Component '{0}' specifies an illegal registry keypath of '{1}'.  Since this entry actually represents a registry key, not a registry value, it cannot be the keypath.
                <Parameter Type="System.String" Name="componentName" />
                <Parameter Type="System.String" Name="registryId" />
            </Instance>
        </Message>
        <Message Id="DeprecatedPatchSequenceTargetAttribute" Number="1082">
            <Instance>
                The {0}/@{1} attribute has been deprecated in favor of the more strongly-typed ProductCode or TargetImage attributes.  Please use the ProductCode attribute for indicating the ProductCode of a patch family directly, or the TargetImage attribute to specify the TargetImage which in turn will retrieve the ProductCode of the patch family.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="ProductIdAuthored" Number="1083">
            <Instance>
                The 'ProductID' property should not be directly authored because it will prevent the ValidateProductID standard action from performing any validation during the installation.  This property will be set by the ValidateProductID standard action or control event.
            </Instance>
        </Message>
        <Message Id="ImplicitMergeModulePrimaryFeature" Number="1084" SourceLineNumbers="no">
            <Instance>
                The merge module '{0}' does not have an explicit primary feature parent specified.  If the source files are linked in a different order, the primary parent feature may change.  To prevent accidental changes, the primary feature parent should be set to 'yes' in one of the MergeRef/@Primary or FeatureGroupRef/@Primary locations for this component.
                <Parameter Type="System.String" Name="componentId" />
            </Instance>
        </Message>
        <Message Id="DeprecatedIgnoreModularizationElement" Number="1085">
            <Instance>
                The IgnoreModularization element has been deprecated.  Use the Binary/@SuppressModularization, CustomAction/@SuppressModularization, or Property/@SuppressModularization attribute instead.
            </Instance>
        </Message>
        <Message Id="PropertyModularizationSuppressed" Number="1086">
            <Instance>
                The Property/@SuppressModularization attribute has been set to 'yes'.  Using this functionality is strongly discouraged; it should only be necessary as a workaround of last resort in rare scenarios.
            </Instance>
        </Message>
        <Message Id="DeprecatedPackageCompressedAttribute" Number="1087">
            <Instance>
                The Package/@Compressed attribute is deprecated under the Module element because merge modules must always be compressed.
            </Instance>
        </Message>
        <Message Id="DeprecatedModuleGuidAttribute" Number="1088">
            <Instance>
                The Module/@Guid attribute is deprecated merge modules use their package code as the modularization guid.  Use the Package/@Id attribute instead.
            </Instance>
        </Message>
        <Message Id="DeprecatedQuestionMarksGuid" Number="1090">
            <Instance>
                The {0}/@{1} attribute's value '????????-????-????-????-????????????' has been deprecated.  Use '*' instead.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="PackageCodeSet" Number="1091">
            <Instance>
                The Package/@Id attribute has been set.  Setting this attribute will allow nonidentical .msi files to have the same package code.  This may be a problem because the package code is the primary identifier used by the installer to search for and validate the correct package for a given installation.  If a package is changed without changing the package code, the installer may not use the newer package if both are still accessible to the installer.  Please remove the Id attribute in order to automatically generate a new package code for each new .msi file.
            </Instance>
        </Message>
        <Message Id="InvalidModuleOrBundleVersion" Number="1093">
            <Instance>
                Invalid {0}/@Version '{1}'. {0} version has a max value of "65535.65535.65535.65535" and must be all numeric.
                <Parameter Type="System.String" Name="moduleOrBundle" />
                <Parameter Type="System.String" Name="version" />
            </Instance>
        </Message>
        <Message Id="InvalidRemoveFile" Number="1095">
            <Instance>
                File '{0}' was removed from component '{1}'. Removing a file from a component will not result in the file being removed by a patch. You should author a RemoveFile element in your component to remove the file from the installation if you want the file to be removed.
                <Parameter Type="System.String" Name="file" />
                <Parameter Type="System.String" Name="component" />
            </Instance>
        </Message>
        <Message Id="PreprocessorWarning" Number="1096">
            <Instance>
                {0}
                <Parameter Type="System.String" Name="message" />
            </Instance>
        </Message>
        <Message Id="UpdateOfNonKeyPathFile" Number="1097" SourceLineNumbers="no">
            <Instance>
                File '{0}' in Component '{1}' was changed, but the KeyPath file '{2}' was not. This file will not be patched on the target system if the REINSTALLMODE does not contain 'A'. The KeyPath file should also be changed and included in your patch.
                <Parameter Type="System.String" Name="nonKeyPathFileId" />
                <Parameter Type="System.String" Name="componentId" />
                <Parameter Type="System.String" Name="keyPathFileId" />
            </Instance>
        </Message>
        <Message Id="UnsupportedCommandLineArgument" Number="1098" SourceLineNumbers="no">
            <Instance>
                '{0}' is not a valid command line argument.
                <Parameter Type="System.String" Name="arg" />
            </Instance>
        </Message>
        <Message Id="MajorUpgradePatchNotRecommended" Number="1099" SourceLineNumbers="no">
            <Instance>
                Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information.
            </Instance>
        </Message>
        <Message Id="RetainRangeMismatch" Number="1100">
            <Instance>
                Mismatch in RetainRangeCounts for the file '{0}' - ignoring the retain ranges.
                <Parameter Type="System.String" Name="fileId"/>
            </Instance>
        </Message>
        <Message Id="DefaultLanguageUsedForVersionedFile" Number="1101">
            <Instance>
                The DefaultLanguage '{0}' was used for file '{1}' which has no language. Specifying a language that is different from the actual file may result in unexpected versioning behavior during a repair or while patching. Either specify a value for DefaultLanguage or put the language in the version information resource to eliminate this warning.
                <Parameter Type="System.String" Name="language"/>
                <Parameter Type="System.String" Name="fileId"/>
            </Instance>
        </Message>
        <Message Id="DefaultLanguageUsedForUnversionedFile" Number="1102">
            <Instance>
                The DefaultLanguage '{0}' was used for file '{1}' which has no language or version. For unversioned files, specifying a value for DefaultLanguage is not neccessary and it will not be used when determining file versions. Remove the DefaultLanguage attribute to eliminate this warning.
                <Parameter Type="System.String" Name="language"/>
                <Parameter Type="System.String" Name="fileId"/>
            </Instance>
        </Message>
        <Message Id="DefaultVersionUsedForUnversionedFile" Number="1103">
            <Instance>
                The DefaultVersion '{0}' was used for file '{1}' which has no version. No entry for this file will be placed in the MsiFileHash table. For unversioned files, specifying a version that is different from the actual file may result in unexpected versioning behavior during a repair or while patching. Version the resource to eliminate this warning.
                <Parameter Type="System.String" Name="version"/>
                <Parameter Type="System.String" Name="fileId"/>
            </Instance>
        </Message>
        <Message Id="InvalidHigherInstallerVersionInModule" Number="1104">
            <Instance>
                Merge module '{0}' has an installer version of {1} which is greater than the product's installer version of {2}. Merging a module with a higher installer version than the product it is being merged into can result in invalid values in the resulting msi. You must set the Package/@InstallerVersion attribute to {1} or greater to merge this merge module into your product.
                <Parameter Type="System.String" Name="moduleId" />
                <Parameter Type="System.Int32" Name="moduleInstallerVersion" />
                <Parameter Type="System.Int32" Name="productInstallerVersion" />
            </Instance>
        </Message>
        <Message Id="ValidationFailedDueToSystemPolicy" Number="1105" SourceLineNumbers="no">
            <Instance>
                Validation could not run due to system policy. To eliminate this warning, run the process as admin or suppress ICE validation.
            </Instance>
        </Message>
        <Message Id="ColumnsIncompatibleWithInstallerVersion" Number="1106">
            <Instance>
                Table '{0}' uses columns that require a version of Windows Installer greater than specified in your package ('{1}').
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.Int32" Name="productInstallerVersion" />
            </Instance>
        </Message>
        <Message Id="TableIncompatibleWithInstallerVersion" Number="1107">
            <Instance>
                Using table '{0}' requires a version of Windows Installer greater than specified in your package ('{1}').
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.Int32" Name="productInstallerVersion" />
            </Instance>
        </Message>
        <Message Id="DeprecatedCommandLineSwitch" Number="1108" SourceLineNumbers="no">
            <Instance>
                The command line switch '{0}' is deprecated.
                <Parameter Type="System.String" Name="oldSwitch" />
            </Instance>
            <Instance>
                The command line switch '{0}' is deprecated. Please use '{1}' instead.
                <Parameter Type="System.String" Name="oldSwitch" />
                <Parameter Type="System.String" Name="newSwitch" />
            </Instance>
        </Message>
        <Message Id="UnexpectedEntrySection" Number="1109">
            <Instance>
                Found mismatched entry point &lt;{0}&gt;. Expected &lt;{1}&gt; for specified output package type {2}.
                <Parameter Type="System.String" Name="sectionType" />
                <Parameter Type="System.String" Name="expectedType" />
                <Parameter Type="System.String" Name="outputExtension" />
            </Instance>
        </Message>
        <Message Id="NewComponentAddedToExistingFeature" Number="1110">
            <Instance>
                Component '{0}' was added to feature '{1}' in the transform '{2}'. If you cannot guarantee that this feature will always be installed, you should consider adding new components to new top-level features to prevent prompts for source when installing this patch.
                <Parameter Type="System.String" Name="component" />
                <Parameter Type="System.String" Name="feature" />
                <Parameter Type="System.String" Name="transformPath" />
            </Instance>
        </Message>
        <Message Id="DeprecatedAttributeValue" Number="1111">
            <Instance>
                The value &quot;{0}&quot; for the {1}/@{2} attribute has been deprecated.  Please use &quot;{3}&quot; instead.
                <Parameter Type="System.String" Name="attributeValue" />
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="newAttributeValue" />
            </Instance>
        </Message>
        <Message Id="InsufficientPermissionHarvestTypeLib" Number="1112" SourceLineNumbers="no">
            <Instance>
                Not enough permissions to harvest type library. On Windows Vista, you must either run Heat elevated, or install Windows Vista SP1 (or higher).
            </Instance>
        </Message>
        <Message Id="UnclearShortcut" Number="1113">
            <Instance>
                Because it is an advertised shortcut, the target of shortcut '{0}' will be the keypath of component '{2}' rather than parent file '{1}'. To eliminate this warning, you can (1) make the Shortcut element a child of the File element that is the keypath of component '{2}', (2) make file '{1}' the keypath of component '{2}', or (3) remove the @Advertise attribute so the shortcut is a non-advertised shortcut.
                <Parameter Type="System.String" Name="shortcutId" />
                <Parameter Type="System.String" Name="fileId" />
                <Parameter Type="System.String" Name="componentId" />
            </Instance>
        </Message>
        <Message Id="TooManyProgIds" Number="1114">
            <Instance>
                Class '{0}' tried to use ProgId '{1}' which has already been associated with class '{2}'. This information will be left out of the decompiled output.
                <Parameter Type="System.String" Name="clsId" />
                <Parameter Type="System.String" Name="progId" />
                <Parameter Type="System.String" Name="otherClsId" />
            </Instance>
        </Message>
        <Message Id="BadColumnDataIgnored" Number="1115">
            <Instance>
                The value '{0}' in table '{1}', column '{2}' is invalid according to the column's validation information. The decompiled output includes a best-effort representation of this value.
                <Parameter Type="System.String" Name="value" />
                <Parameter Type="System.String" Name="tableName" />
                <Parameter Type="System.String" Name="columnName" />
            </Instance>
        </Message>
        <Message Id="NullMsiAssemblyNameValue" Number="1116">
            <Instance>
                The assembly in component '{0}' has a null or empty {1} assembly name value.
                <Parameter Type="System.String" Name="componentName" />
                <Parameter Type="System.String" Name="name" />
            </Instance>
        </Message>
        <Message Id="InvalidAttributeCombination" Number="1117">
            <Instance>
                It is invalid to combine attributes {0} and {1}.  The decompiled output will set attribute {2} to {3}.
                <Parameter Type="System.String" Name="attrib1" />
                <Parameter Type="System.String" Name="attrib2" />
                <Parameter Type="System.String" Name="name" />
                <Parameter Type="System.String" Name="value" />
            </Instance>
        </Message>
        <Message Id="VariableDeclarationCollision" Number="1118">
            <Instance>
                The variable '{0}' with value '{1}' was previously declared with value '{2}'.
                <Parameter Type="System.String" Name="variableName" />
                <Parameter Type="System.String" Name="variableValue" />
                <Parameter Type="System.String" Name="variableCollidingValue" />
            </Instance>
        </Message>
        <Message Id="DuplicatePrimaryKey" Number="1119">
            <Instance>
                The primary key '{0}' is duplicated in table '{1}' and will be ignored. Please remove one of the entries or rename a part of the primary key to avoid the collision.
                <Parameter Type="System.String" Name="primaryKey" />
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="RequiresMsi200for64bitPackage" Number="1121">
            <Instance>
                Package/@InstallerVersion must be 200 or greater for a 64-bit package. The value will be changed to 200. Please specify a value of 200 or greater in order to eliminate this warning.
            </Instance>
        </Message>
        <Message Id="ExternalCabsAreNotSigned" Number="1122" SourceLineNumbers="no">
            <Instance>
                The installer database '{0}' has external cabs, but at least one of them is not signed. Please ensure that all external cabs are signed, if you mean to sign them. If you don't mean to sign them, there is no need to run the insignia tool as part of your build.
                <Parameter Type="System.String" Name="databaseFile" />
            </Instance>
        </Message>
        <Message Id="FailedToDeleteTempDir" Number="1123" SourceLineNumbers="no">
            <Instance>
                Failed to delete temporary directory: {0}
                <Parameter Type="System.String" Name="directory" />
            </Instance>
        </Message>
        <Message Id="StandardDirectoryConflictInMergeModule" Number="1124">
            <Instance>
                The Directory '{0}' starts with the same Id as the standard folder in Windows Installer '{1}'. A directory Id that begins with the same Id as a standard folder that is in an MSM may encounter a conflict when merging the MSM into an MSI. This may result in the contents of this merge module being installed to an unexpected location. To eliminate this warning, change your directory Id to not start with the same Id as any standard folders.
                <Parameter Type="System.String" Name="directory" />
                <Parameter Type="System.String" Name="standardDirectory" />
            </Instance>
        </Message>
        <Message Id="PreprocessorUnknownPragma" Number="1125">
            <Instance>
                The pragma '{0}' is unknown. Please ensure you have referenced the extension that defines this pragma.
                <Parameter Type="System.String" Name="pragmaName" />
            </Instance>
        </Message>
        <Message Id="DeprecatedComponentGroupId" Number="1126">
            <Instance>
                The {0}/@Id attribute contains invalid characters for an identifier. Being able to use invalid identifier characters for a {0} identifier has been deprecated.
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
        </Message>
        <Message Id="UxPayloadsOnlySupportEmbedding" Number="1127">
            <Instance>
                A UX Payload ('{0}') was marked for something other than embedded packaging, possibly because it included a @DownloadUrl attribute. At present, UX Payloads must be embedded in the Bundle, so the requested packaging is being ignored.
                <Parameter Type="System.String" Name="sourceFile" />
            </Instance>
        </Message>
        <Message Id="DiscardedRollbackBoundary" Number="1129">
            <Instance>
                The RollbackBoundary '{0}' was discarded because it was not followed by a package. Without a package the rollback boundary doesn't do anything. Verify that the RollbackBoundary element is not followed by another RollbackBoundary and that the element is not at the end of the chain.
                <Parameter Type="System.String" Name="rollbackBoundaryId" />
            </Instance>
        </Message>
        <Message Id="DeprecatedElement" Number="1130">
            <Instance>
                The {0} element has been deprecated.
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
            <Instance>
                The {0} element has been deprecated.  Please use the {1} element instead.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="newElementName" />
            </Instance>
            <Instance>
                The {0} element has been deprecated.  Please use the {1} or {2} element instead.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="newElementName1" />
                <Parameter Type="System.String" Name="newElementName2" />
            </Instance>
        </Message>
        <Message Id="CannotUpdateCabCache" Number="1131">
            <Instance>
                Cannot update the timestamp of cached cabinet: '{0}'. If the timestamp is not updated, the build may rebuild more than is necessary. To fix the issue, ensure that the cabinet file is writable, error: {1}
                <Parameter Type="System.String" Name="cabinetPath" />
                <Parameter Type="System.String" Name="detail" />
            </Instance>
        </Message>
        <Message Id="DownloadUrlNotSupportedForEmbeddedPayloads" Number="1132">
            <Instance>
                The Payload '{0}' is embedded but included a @DownloadUrl attribute. Embedded Payloads cannot be downloaded so the download URL is being ignored.
                <Parameter Type="System.String" Name="payloadId" />
            </Instance>
        </Message>
        <Message Id="DiscouragedAllUsersValue" Number="1133">
            <Instance>
                Bundles require a package to be either per-machine or per-user. The MSI '{0}' ALLUSERS Property is set to '2' which may change from per-user to per-machine at install time. The Bundle will assume the package is per-{1} and will not work correctly if that changes. If possible, remove the Property with Id='ALLUSERS' and use Package/@InstallScope attribute instead.
                <Parameter Type="System.String" Name="path" />
                <Parameter Type="System.String" Name="machineOrUser" />
            </Instance>
        </Message>
        <Message Id="ImplicitlyPerUser" Number="1134">
            <Instance>
                The MSI '{0}' does not explicitly indicate that it is a per-user package even though the ALLUSERS Property is blank. This suggests a per-user package so the Bundle will assume the package is per-user. If possible, use the Package/@InstallScope attribute to be explicit instead.
                <Parameter Type="System.String" Name="path" />
            </Instance>
        </Message>
        <Message Id="PerUserButForcingPerMachine" Number="1135">
            <Instance>
                The MSI '{0}' is a per-user package being forced to per-machine. Verify that the MsiPackage/@ForcePerMachine attribute is expected and that the per-user package works correctly when forced to install per-machine.
                <Parameter Type="System.String" Name="path" />
            </Instance>
        </Message>
        <Message Id="AttributeShouldContain" Number="1136">
            <Instance>
                The {0}/@{1} attribute value '{2}' should contain '{3}' when the {0}/@{4} attribute is set to '{5}'.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
                <Parameter Type="System.String" Name="attributeValue" />
                <Parameter Type="System.String" Name="expectedContains" />
                <Parameter Type="System.String" Name="otherAttributeName" />
                <Parameter Type="System.String" Name="otherAttributeValue" />
            </Instance>
        </Message>
        <Message Id="DuplicateComponentGuidsMustHaveMutuallyExclusiveConditions" Number="1137">
            <Instance>
                Component/@Id='{0}' has a @Guid value '{1}' that duplicates another component in this package. This is not officially supported by Windows Installer but works as long as all components have mutually-exclusive conditions. It is recommended to give each component its own unique GUID.
                <Parameter Type="System.String" Name="componentId" />
                <Parameter Type="System.String" Name="guid" />
            </Instance>
        </Message>
        <Message Id="DeprecatedRegistryKeyActionAttribute" Number="1138">
            <Instance>
                The RegistryKey/@Action attribute has been deprecated.  In most cases, you can simply omit @Action.  If you need to force Windows Installer to create an empty key or recursively delete the key, use the ForceCreateOnInstall or ForceDeleteOnUninstall attributes instead.
            </Instance>
        </Message>
        <Message Id="NotABinaryWixlib" Number="1139" SourceLineNumbers="no">
          <Instance>
            '{0}' is not a binary Wixlib and has no embedded files.
            <Parameter Type="System.String" Name="wixlib" />
          </Instance>
        </Message>
        <Message Id="NoPerMachineDependencies" Number="1140" SourceLineNumbers="no">
            <Instance>
                Bundle dependencies will not be registered on per-machine packages for a per-user bundle. Either make sure that all packages are installed per-machine, or author any per-machine dependencies as permanent packages.
            </Instance>
        </Message>
        <Message Id="DownloadUrlNotSupportedForAttachedContainers" Number="1141">
            <Instance>
                The Container '{0}' is attached but included a @DownloadUrl attribute. Attached Containers cannot be downloaded so the download URL is being ignored.
                <Parameter Type="System.String" Name="containerId" />
            </Instance>
        </Message>
        <Message Id="ReservedAttribute" Number="1142">
            <Instance>
                The {0}/@{1} attribute is reserved for future use and has no effect in this version of the WiX toolset.
                <Parameter Type="System.String" Name="elementName" />
                <Parameter Type="System.String" Name="attributeName" />
            </Instance>
        </Message>
        <Message Id="RequiresMsi500forArmPackage" Number="1143">
            <Instance>
                Package/@InstallerVersion must be 500 or greater for an Arm package. The value will be changed to 500. Please specify a value of 500 or greater in order to eliminate this warning.
            </Instance>
        </Message>
        <Message Id="RemotePayloadsMustNotAlsoBeCompressed" Number="1144">
            <Instance>
                The {0}/@Compressed attribute must have value 'no' when a RemotePayload child element is present. RemotePayload indicates that a package will always be downloaded and cannot be compressed into a bundle. To eliminate this warning, explicitly set the {0}/@Compressed attribute to 'no'.
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
        </Message>
        <Message Id="AllChangesIncludedInPatch" Number="1145">
            <Instance>
                All changes between the baseline and upgraded packages will be included in the patch except for any change to the ProductCode. The 'All' element is supported primarily for testing purposes and negates the benefits of patch families.
            </Instance>
        </Message>
        <Message Id="RelatedAttributeConditionallyIgnored" Number="1146">
            <Instance>
                Ignoring attribute {0} because attribute {1} is set to {2}.
                <Parameter Type="System.String" Name="recessiveAttribute" />
                <Parameter Type="System.String" Name="dominantAttribute" />
                <Parameter Type="System.String" Name="dominantValue" />
            </Instance>
        </Message>
        <Message Id="NoDifferencesInTransform" Number="1147">
            <Instance>
                The transform did not contain any valid product changes and will not be included in the patch.
            </Instance>
        </Message>
        <Message Id="VersionTruncated" Number="1148">
            <Instance>
                Product version {0} in package '{1}' is not valid per the MSI SDK and cannot be represented in a bundle. It has been truncated to {2}.
                <Parameter Type="System.String" Name="originalVersion" />
                <Parameter Type="System.String" Name="package" />
                <Parameter Type="System.String" Name="truncatedVersion" />
            </Instance>
        </Message>
      <Message Id="DisallowedMsiProperty" Number="1149">
        <Instance>
          The '{0}' MsiProperty is controlled by the bootstrapper and cannot be authored. (Illegal properties are: {1}.) Remove the MsiProperty element. This restriction will be enforced as an error in WiX v4.0.
          <Parameter Type="System.String" Name="property" />
          <Parameter Type="System.String" Name="illegalValueList" />
        </Instance>
      </Message>
        <Message Id="ServiceConfigFamilyNotSupported" Number="1150">
            <Instance>
                {0} functionality is documented in the Windows Installer SDK to "not [work] as expected." Consider replacing {0} with the WixUtilExtension ServiceConfig element.
                <Parameter Type="System.String" Name="elementName" />
            </Instance>
        </Message>
      <Message Id="PayloadMustBeRelativeToCache" Number="1151">
        <Instance>
          The {0}/@{1} attribute's value, '{2}', is not a legal path name: Payload names must be relative to their cache directory and cannot contain '..'.
          <Parameter Type="System.String" Name="elementName" />
          <Parameter Type="System.String" Name="attributeName" />
          <Parameter Type="System.String" Name="attributeValue" />
        </Instance>
      </Message>
    </Class>

    <Class Name="WixVerboses" ContainerName="WixVerboseEventArgs" BaseContainerName="MessageEventArgs" Level="Information">
        <Message Id="ImportBinaryStream" Number="9000" SourceLineNumbers="no">
            <Instance>
                Importing binary stream from '{0}'.
                <Parameter Type="System.String" Name="streamSource" />
            </Instance>
        </Message>
        <Message Id="ImportIconStream" Number="9001" SourceLineNumbers="no">
            <Instance>
                Importing icon stream from '{0}'.
                <Parameter Type="System.String" Name="streamSource" />
            </Instance>
        </Message>
        <Message Id="CopyFile" Number="9002" SourceLineNumbers="no">
            <Instance>
                Copying file '{0}' to '{1}'.
                <Parameter Type="System.String" Name="sourceFile" />
                <Parameter Type="System.String" Name="destinationFile" />
            </Instance>
        </Message>
        <Message Id="MoveFile" Number="9003" SourceLineNumbers="no">
            <Instance>
                Moving file '{0}' to '{1}'.
                <Parameter Type="System.String" Name="sourceFile" />
                <Parameter Type="System.String" Name="destinationFile" />
            </Instance>
        </Message>
        <Message Id="CreateDirectory" Number="9004" SourceLineNumbers="no">
            <Instance>
                The directory '{0}' does not exist, creating it now.
                <Parameter Type="System.String" Name="directory" />
            </Instance>
        </Message>
        <Message Id="RemoveDestinationFile" Number="9005" SourceLineNumbers="no">
            <Instance>
                The destination file '{0}' already exists, attempting to remove it.
                <Parameter Type="System.String" Name="destinationFile" />
            </Instance>
        </Message>
        <Message Id="CabFile" Number="9006" SourceLineNumbers="no">
            <Instance>
                Cabbing file {0} from '{1}'.
                <Parameter Type="System.String" Name="fileId" />
                <Parameter Type="System.String" Name="filePath" />
            </Instance>
        </Message>
        <Message Id="UpdatingFileInformation" Number="9007" SourceLineNumbers="no">
            <Instance>Updating file information.</Instance>
        </Message>
        <Message Id="GeneratingDatabase" Number="9008" SourceLineNumbers="no">
            <Instance>Generating database.</Instance>
        </Message>
        <Message Id="MergingModules" Number="9009" SourceLineNumbers="no">
            <Instance>Merging modules.</Instance>
        </Message>
        <Message Id="CreatingCabinetFiles" Number="9010" SourceLineNumbers="no">
            <Instance>Creating cabinet files.</Instance>
        </Message>
        <Message Id="ImportingStreams" Number="9011" SourceLineNumbers="no">
            <Instance>Importing streams.</Instance>
        </Message>
        <Message Id="LayingOutMedia" Number="9012" SourceLineNumbers="no">
            <Instance>Laying out media.</Instance>
        </Message>
        <Message Id="DecompilingTable" Number="9013" SourceLineNumbers="no">
            <Instance>
                Decompiling the {0} table.
                <Parameter Type="System.String" Name="tableName" />
            </Instance>
        </Message>
        <Message Id="ValidationInfo" Number="9014" SourceLineNumbers="no">
            <Instance>
                {0}: {1}
                <Parameter Type="System.String" Name="ice" />
                <Parameter Type="System.String" Name="message" />
            </Instance>
        </Message>
        <Message Id="CreateCabinet" Number="9015" SourceLineNumbers="no">
            <Instance>
                Creating cabinet '{0}'.
                <Parameter Type="System.String" Name="cabinet" />
            </Instance>
        </Message>
        <Message Id="ValidatingDatabase" Number="9016" SourceLineNumbers="no">
            <Instance>Validating database.</Instance>
        </Message>
        <Message Id="OpeningMergeModule" Number="9017" SourceLineNumbers="no">
            <Instance>
                Opening merge module '{0}' with language '{1}'.
                <Parameter Type="System.String" Name="modulePath" />
                <Parameter Type="System.Int16" Name="language" />
            </Instance>
        </Message>
        <Message Id="MergingMergeModule" Number="9018" SourceLineNumbers="no">
            <Instance>
                Merging merge module '{0}'.
                <Parameter Type="System.String" Name="modulePath" />
            </Instance>
        </Message>
        <Message Id="ConnectingMergeModule" Number="9019" SourceLineNumbers="no">
            <Instance>
                Connecting merge module '{0}' to feature '{1}'.
                <Parameter Type="System.String" Name="modulePath" />
                <Parameter Type="System.String" Name="feature" />
            </Instance>
        </Message>
        <Message Id="ResequencingMergeModuleFiles" Number="9020" SourceLineNumbers="no">
            <Instance>Resequencing files from all merge modules.</Instance>
        </Message>
        <Message Id="BinderTempDirLocatedAt" Number="9021" SourceLineNumbers="no">
            <Instance>
                Binder temporary directory located at '{0}'.
                <Parameter Type="System.String" Name="directory" />
            </Instance>
        </Message>
        <Message Id="ValidatorTempDirLocatedAt" Number="9022" SourceLineNumbers="no">
            <Instance>
                Validator temporary directory located at '{0}'.
                <Parameter Type="System.String" Name="directory" />
            </Instance>
        </Message>
        <Message Id="GeneratingBundle" Number="9023" SourceLineNumbers="no">
            <Instance>
                Generating Burn bundle '{0}' from stub '{1}'.
                <Parameter Type="System.String" Name="bundleFile" />
                <Parameter Type="System.String" Name="stubFile" />
            </Instance>
        </Message>
        <Message Id="ResolvingManifest" Number="9024" SourceLineNumbers="no">
            <Instance>
                Generating resolved manifest '{0}'.
                <Parameter Type="System.String" Name="manifestFile" />
            </Instance>
        </Message>
        <Message Id="LoadingPayload" Number="9025" SourceLineNumbers="no">
            <Instance>
                Loading payload '{0}' into container.
                <Parameter Type="System.String" Name="payload" />
            </Instance>
        </Message>
        <Message Id="BundleGuid" Number="9026" SourceLineNumbers="no">
            <Instance>
                Assigning bundle GUID '{0}'.
                <Parameter Type="System.String" Name="bundleGuid" />
            </Instance>
        </Message>
        <Message Id="CopyingExternalPayload" Number="9027" SourceLineNumbers="no">
            <Instance>
                Copying external payload from '{0}' to '{1}'.
                <Parameter Type="System.String" Name="payload" />
                <Parameter Type="System.String" Name="outputDirectory" />
            </Instance>
        </Message>
        <Message Id="EmbeddingContainer" Number="9028" SourceLineNumbers="no">
            <Instance>
                Embedding container '{0}' ({1} bytes) with '{2}' compression.
                <Parameter Type="System.String" Name="container" />
                <Parameter Type="System.Int64" Name="size" />
                <Parameter Type="System.String" Name="compression" />
            </Instance>
        </Message>
        <Message Id="SwitchingToPerUserPackage" Number="9029" SourceLineNumbers="no">
            <Instance>
                Bundle switching from per-machine to per-user due to addition of per-user package: '{0}'.
                <Parameter Type="System.String" Name="path" />
            </Instance>
        </Message>
        <Message Id="SetCabbingThreadCount" Number="9030" SourceLineNumbers="no">
            <Instance>
                There will be '{0}' threads used to produce CAB files.
                <Parameter Type="System.String" Name="threads" />
            </Instance>
        </Message>
        <Message Id="ValidationSerialized" Number="9031" SourceLineNumbers="no">
            <Instance>
                Multiple packages cannot reliably be validated simultaneously. This validation will resume when the other package being validated has completed.
            </Instance>
        </Message>
        <Message Id="ReusingCabCache" Number="9032">
            <Instance>
                Reusing cabinet '{0}' from cabinet cache path: '{1}'.
                <Parameter Type="System.String" Name="cabinetName" />
                <Parameter Type="System.String" Name="source" />
            </Instance>
        </Message>
        <Message Id="CabinetsSplitInParallel" Number="9033" SourceLineNumbers="no">
            <Instance>
                Multiple Cabinets with Large Files are splitting simultaneously. This current cabinet is waiting on a shared resource and splitting will resume when the other splitting has completed.
            </Instance>
        </Message>
        <Message Id="ValidatedDatabase" Number="9034" SourceLineNumbers="no">
            <Instance>
                Validation complete: {0:N0}ms elapsed.
                <Parameter Type="System.Int64" Name="size" />
            </Instance>
        </Message>
    </Class>
</Messages>
