From d4a96d92b78f7c0085c400f30bd39e6218c057ef Mon Sep 17 00:00:00 2001 From: Rob Mensching Date: Mon, 11 Jul 2022 09:18:46 -0700 Subject: Remove RESX usage in WixToolset.Data Localizing all the messages is not a realistic goal in WiX so no need to manage the overhead related to RESX files. --- src/api/wix/WixToolset.Data/Data/messages.xml | 4038 -------------------- .../Rows/SummaryInfoRowCollection.cs | 3 +- .../wix/WixToolset.Data/WixDataStrings.Designer.cs | 90 - src/api/wix/WixToolset.Data/WixDataStrings.resx | 129 - src/api/wix/WixToolset.Data/WixToolset.Data.csproj | 15 - 5 files changed, 1 insertion(+), 4274 deletions(-) delete mode 100644 src/api/wix/WixToolset.Data/Data/messages.xml delete mode 100644 src/api/wix/WixToolset.Data/WixDataStrings.Designer.cs delete mode 100644 src/api/wix/WixToolset.Data/WixDataStrings.resx (limited to 'src/api') diff --git a/src/api/wix/WixToolset.Data/Data/messages.xml b/src/api/wix/WixToolset.Data/Data/messages.xml deleted file mode 100644 index 5f03fef5..00000000 --- a/src/api/wix/WixToolset.Data/Data/messages.xml +++ /dev/null @@ -1,4038 +0,0 @@ - - - - - - - - - - {0} Exception Type: {1} Stack Trace: {2} - - - - - - - - Unexpected file format loaded from path: {0}. The file was expected to be a {1} but was actually: {2}. Ensure the correct path was provided. - - - - - - - - Attempted to load corrupt file from path: {0}. The file with format {1} contained unexpected content. Ensure the correct path was provided and that the file has not been incorrectly modified. - - - - - - - The localization identifier '{0}' has been duplicated in multiple locations. Please resolve the conflict. - - - - - - The {0} element contains an unexpected attribute '{1}'. - - - - - - - The {0} element contains an unexpected child element '{1}'. - - - - - - - The {0}/@{1} attribute's value cannot be an empty string. If a value is not required, simply remove the entire attribute. - - - - - The {0}/@{1} attribute's value cannot be an empty string. To use the default value "{2}", simply remove the entire attribute. - - - - - - - - The current version of the toolset is {0}, but version {1} is required. - - - - - The current version of the extension '{2}' is {0}, but version {1} is required. - - - - - - - - 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. - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not a legal guid value. - - - - - - - - The {0}/@{1} attribute was not found; it is required. - - - - - The {0} element must have a value for exactly one of the {1} or {2} attributes. - - - - - - - The {0}/@{1} attribute was not found; it is required when attribute {2} is specified. - - - - - - The {0}/@{1} attribute was not found; it is required when attribute {2} has a value of '{3}'. - - - - - - - The {0}/@{1} attribute was not found; it is required unless the attribute {2} has a value of '{3}'. - - - - - - - - - - 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. - - - - - - - - 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. - - - - - - - - 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. - - - - - - - - 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. - - - - - - - - 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. - - - - - 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. - - - - - - 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. - - - - - - The {0}/@{1} attribute's value '{2}' contains an illegal identifier '{3}'. Identifiers may contain ASCII characters A-Z, a-z, digits, underscores (_), or periods (.). Every identifier must begin with either a letter or an underscore. - - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not a legal yes/no value. The only legal values are 'no' and 'yes'. - - - - - - - - Failed to create cab '{0}' while compressing file '{1}' with error 0x{2:X8}. - - - - - - Failed to create cab '{0}' with error 0x{1:X8}. - - - - - - - Failed to extract cab '{0}' to directory '{1}'. This is most likely due to a lack of available disk space on the destination drive. - - - - - 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. - - - - - - - - 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.) - - - - - - - - - The {0}/@{1} attribute cannot be specified because the element is advertised. - - - - - - - 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. - - - - - - The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}'. - - - - - - - The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', or '{4}'. - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', or '{5}'. - - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', or '{6}'. - - - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', '{6}', or '{7}'. - - - - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', '{6}', '{7}', or '{8}'. - - - - - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', '{6}', '{7}', '{8}', or '{9}'. - - - - - - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not one of the legal options: '{3}', '{4}', '{5}', '{6}', '{7}', '{8}', '{9}', or '{10}'. - - - - - - - - - - - - - - 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}'. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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}. - - - - - - - - - - - - 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}. - - - - - - - - - - - - - - The {0} element contains illegal inner text: '{1}'. It may not contain inner text unless the {2} attribute is specified. - - - - - - - - The {0} element requires the {1} attribute because there is no parent {0} element. - - - - - - - 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: \ ? | > < : / * " + , ; = [ ] (space). - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not a valid filename because it contains illegal characters. Legal filenames contain no more than 260 characters and must contain at least one non-period character. Any character except for the follow may be used: \ ? | > < : / * ". - - - - - - The {0}/@{1} attribute's value '{2}' contains a invalid filename '{3}'. Legal filenames contain no more than 260 characters and must contain at least one non-period character. Any character except for the follow may be used: \ ? | > < : / * ". - - - - - - - - - The {0}/@{1} attribute's value, '{2}', is too long for a table name. It cannot be more than than 31 characters long. - - - - - - - - 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. - - - - - - - - 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. - - - - - - - - - - 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. - - - - - - - - - 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. - - - - - - - - - The {0}/{1} element cannot be specified if the {2} attribute's value is '{3}' or '{4}'. - - - - - - - - - - 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'. - - - - - - - - - The {0}/@{1} attribute cannot be specified when attribute {2} is present. - - - - - - The {0}/@{1} attribute cannot be specified when attribute {2} is present with value '{3}'. - - - - - - - - - The {0}/@{1} attribute cannot be specified when attribute {2} or {3} is also present. - - - - - - - The {0}/@{1} attribute cannot be specified when attribute {2}, {3}, or {4} is also present. - - - - - - - - The {0}/@{1} attribute cannot be specified when attribute {2}, {3}, {4}, or {5} is also present. - - - - - - - - - - - The {0}/@{1} attribute can only be specified with the following attribute {2} present. - - - - - - The {0}/@{1} attribute can only be specified with one of the following attributes: {2} or {3} present. - - - - - - - The {0}/@{1} attribute can only be specified with one of the following attributes: {2} or {3} present with value '{4}'. - - - - - - - - - The {0}/@{1} attribute can only be specified with one of the following attributes: {2}, {3}, or {4} present. - - - - - - - - The {0}/@{1} attribute can only be specified with one of the following attributes: {2}, {3}, {4}, or {5} present. - - - - - - - - - - - The {0}/@{1} attribute's value, '{2}', can only be specified with attribute {3} present with value '{4}'. - - - - - - - - The {0}/@{1} attribute's value, '{2}', cannot be specified without attribute {3} present. - - - - - - - - - The integer value {0} collides with a sentinel value in the compiler code. - - - - The long integral value {0} collides with a sentinel value in the compiler code. - - - - - - 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. - - - - - - - - The {0} element contains multiple {1} child elements. There can only be one {1} child element per {0} element. - - - - - - - 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}. - - - - - - - - - - - Failed to close cab '{0}'. - - - - Failed to close cab '{0}', error: {1}. - - - - - - - The {0} element's {1} or {2} attribute was not found; one of these is required. - - - - - - The {0} element's {1}, {2}, or {3} attribute was not found; one of these is required. - - - - - - - The {0} element's {1}, {2}, {3}, or {4} attribute was not found; one of these is required. - - - - - - - - The {0} element's {1}, {2}, {3}, {4}, or {5} attribute was not found; one of these is required. - - - - - - - - - The {0} element's {1}, {2}, {3}, {4}, {5}, or {6} attribute was not found; one of these is required. - - - - - - - - - - The {0} element's {1}, {2}, {3}, {4}, {5}, {6}, or {7} attribute was not found; one of these is required. - - - - - - - - - - - - - The {0} element's {1} or {2} attribute was not found; at least one of these attributes must be specified. - - - - - - The {0} element's {1} or {2} attribute was not found; one of these is required when attribute {3} is present. - - - - - - - The {0} element's {1} or {2} attribute was not found; one of these is required when attribute {3} has a value of '{4}'. - - - - - - - - - - The {0} element's {1} or {2} attribute was not found; one of these is required without attribute {3} present. - - - - - - - - - The {0} element is non-advertised and therefore requires a parent {1} element. - - - - - - - The document element name '{0}' is invalid. A WiX {1} file must use '{2}' as the document element name. - - - - - - - - The {0}/@{1} attribute was not found or empty; it is required, or it can be specified in the parent {2} element. - - - - - - The {0}/@{1} attribute was not found or empty; it is required, or it can be specified in the parent {2}/@{3} attribute. - - - - - - - - - Access to the path '{0}' is denied. - - - - - Cannot set both ExcludeLanguage and ExcludeExceptLanguage attributes on a ModuleExclusion element. - - - - 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'. - - - - - - 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. - - - - - - - The FileTypeMask/@Value and FileTypeMask/@Mask attributes must be the same length. - - - - - Only one search element can appear under a '{0}' element. - - - - - - The {1} attribute can only be specified on the {2} element. - - - - - - - - A '{0}' element must have a search element as a child. - - - - - - Under a '{0}' element, multiple identifiers were found: '{1}' and '{2}'. All search elements under this element must have the same id. - - - - - - - - The advertise state of this element: '{0}', does not match the advertise state set on the parent element: '{1}'. - - - - - - - The context value '{0}' was duplicated. Context values must be distinct. - - - - - - Cannot convert RelativePath into Registry elements. - - - - - 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. - - - - - - - - A {0} element must have at least one child element of type {1}. - - - - - A {0} element must have at least one child element of type {1} or {2}. - - - - - - A {0} element must have at least one child element of type {1}, {2}, or {3}. - - - - - - - A {0} element must have at least one child element of type {1}, {2}, {3}, or {4}. - - - - - - - - - - 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. - - - - - The {0}/@{1} attribute's value, '{2}', is not a legal yes/no/default value. The only legal values are 'default', 'no' or 'yes'. - - - - - - - - The {0}/@{1} attribute cannot be specified in a merge module. - - - - - - Permission elements cannot have GenericRead as the only permission specified. Include at least one other permission. - - - - 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. - - - - - - - A {0} element must have a search element as a child when the {0}/@{1} attribute has the value '{2}'. - - - - - - - - The {0} property was specified. Special MSI properties cannot be authored. Use the attributes on the Property element instead. - - - - - - A {0} element must have a Before attribute, After attribute, or a Sequence attribute. - - - - - - The {0}/@{1} attribute's value, '{2}, is not supported by the Windows Installer. - - - - - - - - A {0} element was specified with Type='{1}' and TabSkip='no'. Tabbable controls are not allowed in Billboards. - - - - - - - A {0} element was specified with Type='{1}' and a CheckBoxValue. Check box values can only be specified with Type='CheckBox'. - - - - - - - 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. - - - - - - - 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. - - - 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. - - - - Illegal value '{0}' for the -sw<N> command line option. Specify a particular warning number, like '-sw6' to suppress the warning with ID 6, or '-sw' alone to suppress all warnings. - - - - - - The variable named '{0}' is not allowed in a foreach expression. - - - - - - Could not find the prefix in parameter name: '{0}'. - - - - - - 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'. - - - - - - - The file with id '{0}' and name '{1}' could not be found with source path: '{2}'. - - - - - - - - {0} - - - - - - Invalid file name '{0}'. - - - - - - A circular reference of groups was detected. The infinite loop includes: {0}. Group references must form a directed acyclic graph. - - - - - - The {0}/@{1} attribute's value, '{2}', is a mixed-case guid. All letters in a guid value should be uppercase. - - - - - - - - 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. - - - - - - - - Multiple entry sections '{0}' and '{1}' found. Only one entry section may be present in a single target. - - - - - - Location of entry section related to previous error. - - - - Duplicate symbol '{0}' found. This typically means that an Id is duplicated. Access modifiers (internal, protected, private) cannot prevent these conflicts. Ensure all your identifiers of a given type (File, Component, Feature) are unique. - - - - Duplicate symbol '{0}' referenced by {1}. This typically means that an Id is duplicated. Ensure all your identifiers of a given type (File, Component, Feature) are unique or use an access modifier to scope the identfier. - - - - - - Location of symbol related to previous error. - - - - Could not find entry section in provided list of intermediates. Expected section of type '{0}'. - - - - - - The identifier '{0}' could not be found. Ensure you have typed the reference correctly and that all the necessary inputs are provided to the linker. - - - - The identifier '{0}' is inaccessible due to its protection level. - - - - - - - Multiple primary references were found for {0} '{1}' in {2} '{3}' and {4} '{5}'. - - - - - - - - - - - Component {0} cannot be contained in a Module twice. - - - - - - 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. - - - - - - - The merge module '{0}' contains 2 or more file identifiers that only differ by case: '{1}' and '{2}'. The WiX 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. - - - - - - - - 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. - - - - - - The localization variable !(loc.{0}) is unknown. Please ensure the variable is defined. - - - - - - The system cannot find the file '{0}'. - - - - The system cannot find the file '{0}' with type '{1}'. - - - - - - - Not a valid {0} file; detail: {1} - - - - - - ProgId elements may not be nested more than 1 level deep. - - - - The DirectorySearchRef {0} can not have a Parent attribute {1} and also be nested under parent element {2} - - - - - - - - Schema validation failed with the following error at line {1}, column {2}: {0} - - - - - - - - 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. - - - - - - - - The {0}/@{1} attribute's value, '{2}', is too long for a table name. It cannot be more than than 31 characters long. - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not a valid column width. Valid column widths are 2 or 4. - - - - - - - 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. - - - - 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". - - - - - - The parameter '{0}' must be followed by a file path. - - - - - - The parameter '{0}' must be followed by a directory path. - - - - - - 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\". - - - - - - 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\\". - - - - - - Additional argument '{0}' was unexpected. Remove the argument and add the '-?' switch for more information. - - - - - - 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'. - - - - - - - - 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. - - - - - - - - - The {0}/@{1} attribute's value, '{2}', contains illegal characters for a family name. Legal values include letters, numbers, and underscores. - - - - - - - - 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. - - - - - - - - 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}. - - - - - - - - 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}. - - - - - - - - - - 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. - - - - - - - - The extension '{0}' contains a definition 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. - - - - - - - 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. - - - - - - - - The process can not access the file '{0}' because it is being used by another process. - - - - - - Cannot open the merge module '{0}' from file '{1}'. - - - - - - - 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. - - - - - - - The file row with identifier '{0}' could not be found. - - - - - - 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} - - - - - - - The end element matching the '{0}' start element was not found. - - - - - - 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. - - - - - - 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}'. - - - - - - - There was an error importing the file '{0}'. - - - - There was an error importing table '{1}' from file '{0}'. - - - - - - - Found an invalid sequence table '{0}'. - - - - - - The directory '{0}' could not be found. - - - - - - The component '{0}' is not assigned to a feature. The component's {1} '{2}' requires it to be assigned to at least one feature. - - - - - - - - The action '{0}' is recursively placed in the '{1}' table. - - - - - - - The {0} file format version {1} is not compatible with the expected {0} file format version {2}. - - - - - - - - The {0} element contains an unexpected xml node of type {1}. - - - - - - - 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. - - - - - - The extension '{0}' could not be loaded. - - - - The extension '{0}' could not be loaded because of the following reason: {1} - - - - - The extension '{0}' is the wrong type: '{1}'. The expected type was '{2}'. - - - - - - The extension '{0}' is the wrong type: '{1}'. The expected type was '{2}' or '{3}'. - - - - - - - - - Found invalid subexpression '{0}' in expression '{1}'. - - - - - - - Found a <?{1}?> processing instruction without a matching <?{0}?> before it. - - - - - - - Found a <?{0}?> processing instruction without a matching <?{1}?> after it. - - - - - - - Expecting an argument for 'NOT' in expression '{0}'. - - - - - - 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})'. - - - - - - Undefined preprocessor variable '$({0})'. - - - - - - The define statement '<?define {0}?>' is not well-formed. Define statements should be in the form <?define variableName = "variable value"?>. - - - - - - The variable '{0}' with value '{1}' was previously declared with value '{2}'. - - - - - - - - The variable '{0}' cannot be undefined because its already undefined. - - - - - - The foreach statement '{0}' is illegal. The proper format for foreach is <?foreach varName in valueList?>. - - - - - - The {0}/@{1} attribute cannot be specified when a {2} element is nested underneath the {0} element. - - - - - - - A <?foreach?> statement was found that had no matching <?endforeach?>. - - - - The quotes don't match in the expression '{0}'. - - - - - - The parenthesis don't match in the expression '{0}'. - - - - - - A required variable was missing in the expression '{0}'. - - - - - - An unexpected literal was found in the expression '{0}'. - - - - - - An illegal number was found in the expression '{0}'. - - - - - - The operator '{0}' is unexpected. - - - - - - The empty subexpression is unexpected in the expression '{0}'. - - - - - - The custom table column '{0}' is unknown. - - - - - - Encountered an unknown custom table column type '{0}'. - - - - - Cannot have both the MsidbFileAttributesCompressed and MsidbFileAttributesNoncompressed options set in a file attributes column. - - - - 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. - - - - - - The location of the action related to previous error. - - - - 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. - - - - - - The location of the action related to previous error. - - - - 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. - - - - - - The location of the non-overridable definition of the action related to previous error. - - - - 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. - - - - - - - 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. - - - - - - - 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. - - - - - - - - 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. - - - - - - - The location of the special termination action related to previous error(s). - - - - 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). - - - - - - - The location of the sequenced action related to previous error. - - - - 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. - - - - - - - - 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. - - - - - - 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. - - - - - - An unexpected row in the '{0}' table was found in this merge module. Merge modules cannot contain the '{0}' table. - - - - - - An unexpected row in the '{0}' table was found in this patch creation package. Patch creation packages cannot contain the '{0}' table. - - - - - - The module '{0}' cannot be merged because it excludes or is excluded by the merge module with signature '{1}'. - - - - - - - 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. - - - - - - - - - The language '{0}' is supported but uses an invalid language transform in the merge module '{1}'. - - - - - - - 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. - - - - - - - Decompilation of the {0} table has not been implemented by its extension. - - - - - - 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. - - - - - Version independent ProgIds cannot have Icons. Remove the Icon and/or IconIndex attributes from your ProgId element. - - - - - The {0}/@{1} attribute's value, '{2}', cannot be specified with attribute {3} present. - - - - - - - The {0}/@{1} attribute's value, '{2}', cannot be specified with attribute {3} present with value '{4}'. - - - - - - - - - - The Merge element '{0}' specified an invalid language '{1}'. Verify that localization tokens are being properly resolved to a numeric LCID. - - - - - - - The WiX variable '{0}' is declared in more than one location. Please remove one of the declarations. - - - - - - The WiX variable '{0}' was declared without a value. Please specify a value for the variable. - - - - - - The WiX 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). - - - - - - The WiX variable $(wix.{0}) uses an illegal prefix '$'. Please use the '!' prefix instead. - - - - - - The {0} element has no namespace. Please make the {0} element look like the following: <{0} xmlns="{1}">. - - - - - The {0} element has an incorrect namespace of '{1}'. Please make the {0} element look like the following: <{0} xmlns="{2}">. - - - - - - - - The {0} element contains an unhandled extension element '{1}'. Please ensure that the extension for elements in the '{2}' namespace has been provided. - - - - - - - - The {0} element contains an unhandled extension attribute '{1}'. Please ensure that the extension for attributes in the '{2}' namespace has been provided. - - - - - - - - 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? - - - - - - - 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? - - - - - - - {0}: {1} - - - - - - - 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'. - - - - - - 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'. - - - - - - The {0} element contains an unexpected child element '{1}'. The '{1}' element may only occur {2} time(s) under the {0} element. - - - - - - - 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'. - - - 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. - - - - 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. - - - - - - - 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'. - - - 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. - - - - 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 WiX localization (.wxl) file. - - - - - - - The merge module '{0}' is not assigned to a feature. All merge modules must be assigned to at least one feature. - - - - - - An unexpected Win32 exception with error code 0x{0:X} occurred: {1} - - - - - An unexpected Win32 exception with error code 0x{0:X} occurred while accessing file '{1}': {2} - - - - - - - - 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: "{0}". - - - - 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: "{0}". - - - - - - - Illegal number of threads to create cabinets: '{0}' for -ct <N> command line option. Specify the number of threads to use like -ct 2. - - - - - - The {0} environment variable is set to an invalid value of '{1}'. - - - - - - - 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. - - - - - - - - - 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. - - - - - - - - - - - The cube file '{0}' cannot be found. This file is required for MSI validation. - - - - - - Failed to open database '{0}'. Ensure it is a valid database, and it is not open by another process. - - - - - - The types of the outputs do not match. One output's type is '{0}' while the other is '{1}'. - - - - - - - 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. - - - - - - 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. - - - - - - - - The transform being built did not contain any differences so it could not be created. - - - - - The code pages of the outputs do not match. One output's code page is '{0}' while the other is '{1}'. - - - - - - - The location of the mismatched code page related to the previous warning. - - - - - 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. - - - 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. - - - - - - 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.) - - - - - - - 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." - - - - - The CustomAction sets a property but its Execute attribute is not 'immediate' (the default). Property-setting custom actions cannot be deferred." - - - - - 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. - - - - - - Undefined preprocessor function '$({0})'. - - - - - - In the preprocessor extension that handles prefix '{0}' while trying to call function '{1}({2})' and exception has occurred : {3} - - - - - - - - - In the preprocessor extension that handles prefix '{0}' while trying to get the value for variable '{1}' and exception has occured : {2} - - - - - - - - The manifest '{0}' does not have the required assembly/assemblyIdentity element. - - - - - - The file '{0}' is not a valid WiX Transform. - - - - - - The file '{0}' has an unexpected extension. Expected one of the following: '{1}'. - - - - - - - An unexpected row in the '{0}' table was found in this patch. Patches cannot contain the '{0}' table. - - - - - - 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. - - - - 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. - - - - - - - Component '{0}' has a changed keypath in the transform '{1}'. Patches cannot change the keypath of a component. - - - - - - - The validator requires at least one extension. Add "ValidatorExtension, Wix" for the default implementation. - - - - - Unknown validation message type '{0}'. - - - - - - No transforms were provided to attach to the patch. - - - - - Multiple extensions were specified on the command line, only a single extension is supported. - - - - - The transform {0} was included twice on the command line. Each transform can be applied to a patch only once. - - - - - - No baseline was specified for one of the transforms specified. A baseline is required for all transforms in a patch. - - - - - {0} - - - - - - {0} is expected to be followed by a value argument. - - - - - - 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. - - - - - No decompiler was provided. {0} requires a decompiler. - - - - - - The table '{0}' was expected but was missing. - - - - - - The {0} element cannot have a child element '{1}' unless attribute '{2}' is set to '{3}'. - - - - - - - The {0} element cannot have a child element '{1}' unless attribute '{2}' is set to '{3}' or '{4}'. - - - - - - - - - - The WixMsp is missing the patch ID. - - - - - The WixMsp has no media rows defined. - - - - - The file '{0}' cannot be found. - - - - - - The WixMsp is missing the client patch ID. Recompile the patch source files with the latest WiX toolset. - - - - - Product '{0}': Table '{1}' has a new row '{2}' added. This makes the patch not uninstallable. - - - - - - - - This patch is not uninstallable. The 'Patch' element's attribute 'AllowRemoval' should be set to 'no'. - - - - - '{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. - - - - - - '{0}' is too large, file size must be less than 2147483648. - - - - - - The parameter '{0}' is missing or has an invalid value {1}. Possible values are x86, x64, or ia64. - - - - - - - The Platform attribute has an invalid value {0}. Possible values are x86, x64, or ia64. - - - - - - You may only specify a single default type using -t or specify custom validation using -serr and -val. - - - - - 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. - - - - - - '-{0}' cannot be specfied in combination with '-{1}'. - - - - - - - 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. - - - - - 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}. - - - - - - - - - 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. - - - - - - - - - File '{0}' is marked as a Win32 assembly but it refers to assembly manifest '{1}' that is not present in this product. - - - - - - - Unable to open merge module '{0}'. Check to make sure the module language is correct. '{1}' - - - - - - - The '{0}/@{1}' attribute was not found; it is required when element '{0}' is not nested under a '{2}' element. - - - - - - - - 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. - - - - - - - - The code page '{0}' is not a valid Windows code page. Please check the {1}/@{2} attribute value in your source file. - - - - - - - - The compression level '{0}' is not valid. Valid values are 'none', 'low', 'medium', 'high', and 'mszip'. - - - - - The transform schema does not match the database schema. The transform may have been generated from a different database. - - - - 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. - - - - - - The {0} option requires a directory, but the provided path is a file: {1} - - - - - - - The {0} option requires a file, but the provided path is a directory: {1} - - - - - - - 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. - - - - - - - Error writing to the path: '{0}'. Error message: '{1}' - - - - - - - Invalid file name specified on the command line: '{0}'. Error message: '{1}' - - - - - - - When the {0}/@{1} attribute is specified, the {0} element must be nested under a {2} element. - - - - - - - - Illegal value '{0}' for the -wx<N> 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. - - - - - - Element '{0}' missing attribute '{1}' or child element '{2}'. Exactly one of those is required. - - - - - - - - The variable '{0}' with value '{1}' was previously declared with value '{2}'. - - - - - - - - The variable definition '{0}' is not valid. Variable definitions should be in the form -dname=value where the value is optional. - - - - - - Duplicate cabinet name '{0}' found. - - - - - - Duplicate cabinet name '{0}' error related to previous error. - - - - - - 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. - - - - - - 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. - - - - - - 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. - - - - - - - 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. - - - - - 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. - - - - - Unresolved bind-time variable {0}. - - - - - - 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. - - - - - - - Illegal characters in path '{0}'. Ensure you provided a valid path to the file. - - - - - - 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. - - - - - You must specify an output file using the "-o" or "-out" switch when you provide more than one input file. - - - - - 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. - - - - - - - The {0}/@{1} attribute's value, '{2}', is too long. {0}/@{1} attribute's must be {3} characters long or less. - - - - - - - - - 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. - - - - - - - - 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. - - - - - Either '{1}' was not defined in the assembly or the type defined in extension '{0}' could not be loaded. - - - - - The extension type '{1}' in extension '{0}' does not inherit from the expected class '{2}'. - - - - - - The type '{1}' in extension '{0}' could not be loaded. Exception type '{2}' returned the following message: {3} - - - - - - - - - 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. - - - - - 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. - - - - - 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. - - - - - - 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. - - - - - - The DirectorySearch element '{0}' requires that the child {1} element has a unique Id when the DirectorySearch/@AssignToProperty attribute is set to 'yes'. - - - - - - - The {0}/@{1} attribute value, '{2}', cannot be specified when the {0} element is nested underneath a {3} element. - - - - - - - - - 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. - - - - - - 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. - - - - - - 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. - - - - - - - - A harvest source must be specified after the harvest type and can be followed by harvester arguments. - - - - - The '-out' or '-o' parameter must specify a file path. - - - - - The command line option '{0}' has already been loaded by another Heat extension. - - - - - - The harvest type was not found in the list of loaded Heat extensions. - - - The harvest type '{0}' was specified. Harvest types cannot start with a '-'. Remove the '-' to specify a valid harvest type. - - - - - - 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. - - - - - Illegal binder class name specified for -binder command line option. - - - - - The specified binder class '{0}' was not found in any extensions. - - - - - - Cannot load binder file manager: {0}. Light can only load one binder file manager and has already loaded binder file manager: {1}. - - - - - - - Cannot load linker extension: {0}. Light can only load one link extension and has already loaded link extension: {1}. - - - - - - - Unable to get the authenticode certificate of '{0}'. More information: {1} - - - - - - - Unable to get the authenticode certificate of '{0}'. The cryptography API has limitations on Windows XP and Windows Server 2003. More information: {1} - - - - - - - Unable to output to file '{0}' because it is marked as read-only. - - - - - - The Component/@Id attribute was not found; it is required when there is no valid keypath to use as the default id value. - - - - - The parent {0} element is missing the {1} attribute that is required for the {2} child element. - - - - - - - - Exception thrown while processing pragma '{0}'. The exception's message is: {1} - - - - - - - Malformed preprocessor pragma '{0}'. Pragmas must have a prefix, a name of at least 1 character long, and be followed by optional arguments. - - - - - - Unknown input file format - expected a .msi or .msm file. - - - - - Files with an extension of .msp are not currently supported. - - - - - Path contains one or more invalid characters. - - - - - Stub executable '{0}' is not a valid Win32 executable. - - - - - - Stub executable '{0}' does not contain a .wixburn data section. - - - - - - Stub executable '{0}' .wixburn data section is too small to store the Burn container header. - - - - - - The Bundle is missing '{0}' data, and cannot continue. - - - - - - A group parent ('{0}'/'{1}') had an unexpected child ('{2}'/'{3}'). - - - - - - - - - A circular reference of ordering dependencies was detected. The infinite loop includes: {0}. Ordering dependency references must form a directed acyclic graph. - - - - - - An expected identifier ('{1}', of type '{0}') was not found. - - - - - - - '{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. - - - - - - 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: ? | > < : / * ". - - - - - - - - The {0}/@{1} attribute's value, '{2}', is not one of the legal options: {3}. - - - - - - - - - The {0}/@{1} attribute's value, '{2}', is one of the illegal options: {3}. - - - - - - - - - - The code page '{0}' is invalid for summary information. You must specify an ANSI code page. - - - - - - The package being validated requires a higher version of Windows Installer than is installed on this machine. Validation cannot continue. - - - - - 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. - - - - - - - Unable to read package '{0}'. {1} - - - - - - - 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. - - - - - - - Unable to read bundle executable '{0}'. This is not a valid WiX bundle. - - - - - - 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 WiX in order to read this bundle. - - - - - - - - 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. - - - - - - - Only one of Media and MediaTemplate tables should be authored. - - - - - 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: \ ? | > < : / * " + , ; = [ ] (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). - - - - - - '{0}' is too large. Reduce the size of maximum uncompressed media size. - - - - - - File '{0}' could not be verified with a catalog file. - - - - - - Could not get hash of file '{0}'. Error: {2}. - - - - - - - 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. - - - - - - - - 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. - - - - - - 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. - - - - - - - The '{0}' MsiProperty is controlled by the bootstrapper and cannot be authored. (Illegal properties are: {1}.) Remove the MsiProperty element. - - - - - - - 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. - - - - - - - - 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. - - - - - 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. - - - - - 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. - - - - - - - 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. - - - - - - - The provider dependency version was not authored for the package with Id '{0}'. Please author the Provides/@Version attribute for this package. - - - - - - - The {0} element cannot have a child element '{1}' when attribute '{2}' is set. - - - - - - - - The {0} element must have attribute '{1}' when child element '{2}' is present. - - - - - - - - The localization for control {0} in dialog {1} is duplicated. Only one localization per control is allowed. - - - - - The localization for dialog {0} is duplicated. Only one localization per dialog is allowed. - - - - - - '{0}' is too large. Reduce the size of maximum cabinet size for large file splitting. The maximum permitted value is '{1}' MB. - - - - - - - Failed to register the copy command for cabinet '{0}' formed by splitting cabinet '{1}'. - - - - - - - The cabinet name '{0}' collides with the new cabinet formed by splitting cabinet '{1}', consider renaming cabinet '{0}'. - - - - - - - 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. - - - - - - - - Invalid AutoVersion template specified. - - - - - Invalid {0}/@Version '{1}'. {0} version has a max value of "65535.65535.65535.65535" and must be all numeric. - - - - - - - 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. - - - - - - - There is no media defined for disk id '{0}'. You must author either <Media Id='{0}' ...> or <MediaTemplate ...>. - - - - - - The RemotePayload element can only be used for ExePackage and MsuPackage payloads. - - - - - The {0}/@{1} attribute's value, '{2}', is not a legal yes/no/always value. The only legal values are 'always', 'no' or 'yes'. - - - - - - - - Include files cannot be nested more deeply than {0} times. Make sure included files don't accidentally include themselves. - - - - - - The table '{0}' contains {1} columns which is not supported by Windows Installer. Windows Installer supports a maximum of {2} columns. - - - - - - - - The {0}/@{1} attribute's value '{2}' only specifies a directory reference. The inline directory syntax requires that at least one directory be specified in addition to the value. For example, use '{3}:\foo\' to add a 'foo' directory. - - - - - - - - - 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. - - - - - - 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 '..'. - - - - - - - - MSI transactions must install all x64 packages before any x86 package. - - - - - - - - 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). - - - - - - - - - - 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. - - - - - - - Unable to find existing file {0} to place in src location {1}. Will likely cause a linker break. - - - - - - Since the CopyFile/@FileId attribute was specified but none of the following attributes (DestinationName, DestinationDirectory, DestinationProperty) were specified, this authoring will not do anything. - - - - The {0}.{1} column's value, '{2}', indicates a nested install. Nested installations are not supported by the WiX team. This action will be left out of the decompiled output. - - - - - - - - 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). - - - - - - Property '{0}' does not contain a Value attribute and is not marked as Admin, Secure, or Hidden. The Property element is being ignored. - - - - - 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. - - - - The action '{0}' in the {1} table is being suppressed. - - - - - - - The merged action '{0}' in the {1} table is being suppressed. - - - - - - - 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. - - - - - Access denied; cannot delete '{0}'. - - - - - - The directory '{0}' is in use and cannot be deleted. - - - - - - Access denied; cannot set attributes on '{0}'. - - - - - - 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. - - - - - - - The {0}/@{1} attribute's value, '{2}', is too long for an identifier. Standard identifiers are 72 characters long or less. - - - - - - - - The {0} table contains a row with primary key '{1}' which has an unknown permission at bit {2}. - - - - - - - - The {0} element's {1} and {2} values are both '{3}'. This is redundant; the {2} attribute should be removed. - - - - - - - The {0} element's source and destination names are identical. This is redundant; the {1} and {2} attributes should be removed if present. - - - - - - - Unable to reset acls on destination files. - - - - 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: \ ? | > < : / * " + , ; = [ ] (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). - - - - - - - - The built-in preprocessor variable '{0}' is deprecated. Please correct your authoring to use the new '{1}' preprocessor variable instead. - - - - - - - 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. - - - - - - - - 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'). - - - - - - - - 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. - - - - - - 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. - - - - - - 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. - - - - - - - - The location of the action related to previous warning. - - - The location of the suppressed action related to previous warning. - - - - An unexpected row in the '{0}' table was found in this product. Products should not contain the '{0}' table. - - - - - - The {0}/@{1} attribute has been deprecated. - - - - - The {0}/@{1} attribute has been deprecated. Please use the {2} attribute instead. - - - - - - The {0}/@{1} attribute has been deprecated. Please use the {2} or {3} attribute instead. - - - - - - - - - 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. - - - - - - - - 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. - - - - - - - - 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 WiX automatically sequence it. - - - - - - - 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. - - - - - - - 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. - - - - - - - - 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. - - - - - - - - - - - - The {0} table is being decompiled as a custom table. - - - - - - The {0} table is not legal in a patch creation file. The information in this table will be left out of the decompiled output. - - - - - - The {0} table can only be represented in WiX for merge modules. The information in this table will be left out of the decompiled output. - - - - - - The {0} table can only be represented in WiX for patch creation files. The information in this table will be left out of the decompiled output. - - - - - - The {0}.{1} column's value, '{2}', cannot currently be represented in the WiX schema. - - - - - - - - The {0} table is not supported by the WiX toolset because it has been deprecated by the Windows Installer team. Any information in this table will be left out of the decompiled output. - - - - - - 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. - - - - - - The {0}.{1} column's value, '{2}', is not a recognized legal value. This information will be left out of the decompiled output. - - - - - - - - The {0}/@{1} attribute has been deprecated. Since WiX 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 WiX 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. - - - - - - - - - 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. - - - - - - The location of a conflicting generated short file name related to the previous warning. - - - - - 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. - - - - - - 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. - - - - - - The {0}/@{1} attribute's value, '{2}', is a placeholder value used in example files. Please replace this placeholder with the appropriate value. - - - - - - - The Product/@UpgradeCode attribute was not found; it is strongly recommended to ensure that this product can be upgraded. - - - - {0}: {1} - - - - - - - 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. - - - - - - 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. - - - - 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. - - - - 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. - - - - - - 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. - - - - 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. - - - - - - - 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. - - - - - - - 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. - - - - - 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. - - - - - - The IgnoreModularization element has been deprecated. Use the Binary/@SuppressModularization, CustomAction/@SuppressModularization, or Property/@SuppressModularization attribute instead. - - - - - 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. - - - - - The Package/@Compressed attribute is deprecated under the Module element because merge modules must always be compressed. - - - - - The Module/@Guid attribute is deprecated merge modules use their package code as the modularization guid. Use the Package/@Id attribute instead. - - - - - The {0}/@{1} attribute's value '????????-????-????-????-????????????' has been deprecated. Use '*' instead. - - - - - - - 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. - - - - - Invalid {0}/@Version '{1}'. {0} version has a max value of "65535.65535.65535.65535" and must be all numeric. - - - - - - - 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. - - - - - - - {0} - - - - - - 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. - - - - - - - - '{0}' is not a valid command line argument. - - - - - - 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. - - - - - Mismatch in RetainRangeCounts for the file '{0}' - ignoring the retain ranges. - - - - - - 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. - - - - - - - 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. - - - - - - - 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. - - - - - - - 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. - - - - - - - - Validation could not run due to system policy. To eliminate this warning, run the process as admin or suppress ICE validation. - - - - - Table '{0}' uses columns that require a version of Windows Installer greater than specified in your package ('{1}'). - - - - - - - Using table '{0}' requires a version of Windows Installer greater than specified in your package ('{1}'). - - - - - - - The command line switch '{0}' is deprecated. - - - - The command line switch '{0}' is deprecated. Please use '{1}' instead. - - - - - - - Found mismatched entry point <{0}>. Expected <{1}> for specified output package type {2}. - - - - - - - - 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. - - - - - - - - The value "{0}" for the {1}/@{2} attribute has been deprecated. Please use "{3}" instead. - - - - - - - - - Not enough permissions to harvest type library. On Windows Vista, you must either run Heat elevated, or install Windows Vista SP1 (or higher). - - - - - 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. - - - - - - - - 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. - - - - - - - - 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. - - - - - - - - The assembly in component '{0}' has a null or empty {1} assembly name value. - - - - - - - It is invalid to combine attributes {0} and {1}. The decompiled output will set attribute {2} to {3}. - - - - - - - - - The variable '{0}' with value '{1}' was previously declared with value '{2}'. - - - - - - - - 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. - - - - - - - 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. - - - - - 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. - - - - - - Failed to delete temporary directory: {0} - - - - - - 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. - - - - - - - The pragma '{0}' is unknown. Please ensure you have referenced the extension that defines this pragma. - - - - - - The {0}/@Id attribute contains invalid characters for an identifier. Being able to use invalid identifier characters for a {0} identifier has been deprecated. - - - - - - 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. - - - - - - 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. - - - - - - The {0} element has been deprecated. - - - - The {0} element has been deprecated. Please use the {1} element instead. - - - - - The {0} element has been deprecated. Please use the {1} or {2} element instead. - - - - - - - - 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} - - - - - - - The Payload '{0}' is embedded but included a @DownloadUrl attribute. Embedded Payloads cannot be downloaded so the download URL is being ignored. - - - - - - 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. - - - - - - - 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. - - - - - - 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. - - - - - - The {0}/@{1} attribute value '{2}' should contain '{3}' when the {0}/@{4} attribute is set to '{5}'. - - - - - - - - - - - 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. - - - - - - - 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. - - - - - '{0}' is not a binary Wixlib and has no embedded files. - - - - - - Bundle dependencies will not be registered on per-machine package '{0}' for a per-user bundle. Either make sure that all packages are installed per-machine, or author any per-machine dependencies as permanent packages. - - - - - - The Container '{0}' is attached but included a @DownloadUrl attribute. Attached Containers cannot be downloaded so the download URL is being ignored. - - - - - - The {0}/@{1} attribute is reserved for future use and has no effect in this version of the WiX toolset. - - - - - - - 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. - - - - - 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'. - - - - - - 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. - - - - - Ignoring attribute {0} because attribute {1} is set to {2}. - - - - - - - - Backslash terminate the {0}/@{1} attribute's inline directory value '{2}'. A backslash ensures a directory name will not be mistaken for a directory reference. - - - - - - - - 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}. - - - - - - - - {0} functionality is documented in the Windows Installer SDK to "not [work] as expected." Consider replacing {0} with the WixUtilExtension ServiceConfig element. - - - - - - - - - Importing binary stream from '{0}'. - - - - - - Importing icon stream from '{0}'. - - - - - - Copying file '{0}' to '{1}'. - - - - - - - Moving file '{0}' to '{1}'. - - - - - - - The directory '{0}' does not exist, creating it now. - - - - - - The destination file '{0}' already exists, attempting to remove it. - - - - - - Cabbing file {0} from '{1}'. - - - - - - Updating file information. - - - Generating database. - - - Merging modules. - - - Creating cabinet files. - - - Importing streams. - - - Laying out media. - - - - Decompiling the {0} table. - - - - - - {0}: {1} - - - - - - - Creating cabinet '{0}'. - - - - - Validating database. - - - - Opening merge module '{0}' with language '{1}'. - - - - - - - Merging merge module '{0}'. - - - - - - Connecting merge module '{0}' to feature '{1}'. - - - - - - Resequencing files from all merge modules. - - - - Binder temporary directory located at '{0}'. - - - - - - Validator temporary directory located at '{0}'. - - - - - - Generating Burn bundle '{0}' from stub '{1}'. - - - - - - - Generating resolved manifest '{0}'. - - - - - - Loading payload '{0}' into container. - - - - - - Assigning bundle GUID '{0}'. - - - - - - Copying external payload from '{0}' to '{1}'. - - - - - - - Embedding container '{0}' ({1} bytes) with '{2}' compression. - - - - - - - - Bundle switching from per-machine to per-user due to addition of per-user package '{0}'. - - - - - - There will be '{0}' threads used to produce CAB files. - - - - - - Multiple packages cannot reliably be validated simultaneously. This validation will resume when the other package being validated has completed. - - - - - Reusing cabinet '{0}' from cabinet cache path: '{1}'. - - - - - - - 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. - - - - - Validation complete: {0:N0}ms elapsed. - - - - - diff --git a/src/api/wix/WixToolset.Data/WindowsInstaller/Rows/SummaryInfoRowCollection.cs b/src/api/wix/WixToolset.Data/WindowsInstaller/Rows/SummaryInfoRowCollection.cs index 4b2ce129..58054f7c 100644 --- a/src/api/wix/WixToolset.Data/WindowsInstaller/Rows/SummaryInfoRowCollection.cs +++ b/src/api/wix/WixToolset.Data/WindowsInstaller/Rows/SummaryInfoRowCollection.cs @@ -18,8 +18,7 @@ namespace WixToolset.Data.WindowsInstaller.Rows { if (0 != String.CompareOrdinal("_SummaryInformation", table.Name)) { - string message = string.Format(WixDataStrings.EXP_UnsupportedTable, table.Name); - throw new ArgumentException(message, "table"); + throw new ArgumentException($"The table {table.Name} is not supported.", "table"); } foreach (Row row in table.Rows) diff --git a/src/api/wix/WixToolset.Data/WixDataStrings.Designer.cs b/src/api/wix/WixToolset.Data/WixDataStrings.Designer.cs deleted file mode 100644 index de26156a..00000000 --- a/src/api/wix/WixToolset.Data/WixDataStrings.Designer.cs +++ /dev/null @@ -1,90 +0,0 @@ -//------------------------------------------------------------------------------ -// -// This code was generated by a tool. -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -//------------------------------------------------------------------------------ - -namespace WixToolset.Data { - using System; - - - /// - /// A strongly-typed resource class, for looking up localized strings, etc. - /// - // This class was auto-generated by the StronglyTypedResourceBuilder - // class via a tool like ResGen or Visual Studio. - // To add or remove a member, edit your .ResX file then rerun ResGen - // with the /str option, or rebuild your VS project. - [global::System.CodeDom.Compiler.GeneratedCodeAttribute("System.Resources.Tools.StronglyTypedResourceBuilder", "16.0.0.0")] - [global::System.Diagnostics.DebuggerNonUserCodeAttribute()] - [global::System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class WixDataStrings { - - private static global::System.Resources.ResourceManager resourceMan; - - private static global::System.Globalization.CultureInfo resourceCulture; - - [global::System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1811:AvoidUncalledPrivateCode")] - internal WixDataStrings() { - } - - /// - /// Returns the cached ResourceManager instance used by this class. - /// - [global::System.ComponentModel.EditorBrowsableAttribute(global::System.ComponentModel.EditorBrowsableState.Advanced)] - public static global::System.Resources.ResourceManager ResourceManager { - get { - if (object.ReferenceEquals(resourceMan, null)) { - global::System.Resources.ResourceManager temp = new global::System.Resources.ResourceManager("WixToolset.Data.WixDataStrings", typeof(WixDataStrings).Assembly); - resourceMan = temp; - } - return resourceMan; - } - } - - /// - /// Overrides the current thread's CurrentUICulture property for all - /// resource lookups using this strongly typed resource class. - /// - [global::System.ComponentModel.EditorBrowsableAttribute(global::System.ComponentModel.EditorBrowsableState.Advanced)] - public static global::System.Globalization.CultureInfo Culture { - get { - return resourceCulture; - } - set { - resourceCulture = value; - } - } - - /// - /// Looks up a localized string similar to The value '{0}' is not a legal identifier and therefore cannot be modularized.. - /// - public static string EXP_CannotModularizeIllegalID { - get { - return ResourceManager.GetString("EXP_CannotModularizeIllegalID", resourceCulture); - } - } - - /// - /// Looks up a localized string similar to Unknown column type: {0}. - /// - public static string EXP_UnknownColumnType { - get { - return ResourceManager.GetString("EXP_UnknownColumnType", resourceCulture); - } - } - - /// - /// Looks up a localized string similar to The table {0} is not supported.. - /// - public static string EXP_UnsupportedTable { - get { - return ResourceManager.GetString("EXP_UnsupportedTable", resourceCulture); - } - } - } -} diff --git a/src/api/wix/WixToolset.Data/WixDataStrings.resx b/src/api/wix/WixToolset.Data/WixDataStrings.resx deleted file mode 100644 index 999f5057..00000000 --- a/src/api/wix/WixToolset.Data/WixDataStrings.resx +++ /dev/null @@ -1,129 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - text/microsoft-resx - - - 2.0 - - - System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - - - The table {0} is not supported. - - - The value '{0}' is not a legal identifier and therefore cannot be modularized. - - - Unknown column type: {0} - - \ No newline at end of file diff --git a/src/api/wix/WixToolset.Data/WixToolset.Data.csproj b/src/api/wix/WixToolset.Data/WixToolset.Data.csproj index 980440ea..e2d71e87 100644 --- a/src/api/wix/WixToolset.Data/WixToolset.Data.csproj +++ b/src/api/wix/WixToolset.Data/WixToolset.Data.csproj @@ -14,21 +14,6 @@ $(NoWarn);CS1591 - - - True - True - WixDataStrings.resx - - - - - - PublicResXFileCodeGenerator - WixDataStrings.Designer.cs - - - -- cgit v1.2.3-55-g6feb