Torch schema exception on CustomTable Column definitions without a Set attribute

[wixbot]

There seems to be an issue in the released version of 3.6 where Torch throws an invalid schema exception for CustomTables which do not define the "Set" attribute on one or more Column definitions.

example:
error TRCH0107 : Schema validation failed with the following error at line 1, column 18611: The 'set' attribute has an invalid value according to its data type.

It seems to be an issue in how Light writes out unspecified Set attribute values to the .wixpdb file -- it writes an empty string instead of not specifying anything at all.

That is:

  

Passing the resulting .wixpdb into Torch results in the schema exception given above.

Originally opened by rvdwagner from http://sourceforge.net/p/wix/bugs/3142/

[wixbot]

Here's an example... The names and descriptions are changed, but the table is as we've defined it.

      <CustomTable Id='CustomTable'>
          <Column Id='Column1' Category='Identifier' Type='string' Width='72'
                        Description='The identifier for the row'
                        Localizable='no' Nullable='no' PrimaryKey='yes' />
          <Column Id='Column2' Category='Condition' Type='string' Width='255'
                        Description='A random condition'
                        Localizable='no' Nullable='yes' PrimaryKey='no'
                        Modularize='Condition' />
          <Column Id='Column3' Category='Integer' Type='int' Width='2'
                        Nullable='no' MinValue='1' MaxValue='9999' 
                        Description='A random value'
                        PrimaryKey='no' />
      </CustomTable>

[wixbot]

I also noticed this same schema exception occurring in Light when consuming a .wixout file generated earlier by that same version of Light in order to generate the final .msi.

But, given it's likely an issue with how Light writes out such tables, it's not surprising the symptoms show up in more than one application.

[wixbot]

Please post your definition.

[wixbot]

That was supposed to be: Please post your CustomTable definition.

[wixbot]

Originally changed by barnson
Area set to linker
Release changed from v3.8 to v3.x

[wixbot]

Originally changed by bmurri
AssignedTo set to wixsupport

[wixbot]

This is still happening for 3.8. We're also not able to read the wixpdb file to try and work around it since it's in cab format.

Originally posted by djryan
Status changed from Open to Untriaged

[wixbot]

Known issue, open to fixed in v3.x.

[wixbot]

Originally changed by barnson
AssignedTo changed from wixsupport to bobarnson
Release changed from v3.x to v3.9

[wixbot]

wixtoolset/wix3#64

Originally posted by barnson

[wixbot]

Originally changed by barnson
Resolution set to fixed
Status changed from Open to Resolved

[wixbot]

I downloaded 3.9 RC3 but am still getting this error. Has this not been fixed?

Originally posted by pezmannen

[wixbot]

@pezmannen, it was fixed. Please provide a sample project that demonstrates the problem.

Originally posted by barnson