The documentation for the _Validation
table specifies that the table should not be included in shipped installer databases, but the ICE tests shipped with msival2.exe and Orca require the tables to be present.
I suspect that I have to merge a MSM containing all standard tables and a populated _Validation
table prior to running the validation suite, but that has a lot of drawbacks:
- only supports standard tables
- doesn't flag an error if a standard table is missing in the shipped MSI
- needs to modify the Installer database prior to validation
Should I just ignore the advice and ship my _Validation
table inside the release MSI, or is there a better way?