Fortunately, I'm not using the tables that are mentioned so, as far as I can tell, this isn't an issue at the moment. Still, it would be preferable if the schema could be set according to the minimum Installer version specified, or something, so that those warnings could be eliminated and maybe prevent potential problems down the road (just in case).Complete functionality of the MsiPatchCertificate table is only available with Windows Installer version 3.0. Your schema is 200.
Is there a way to specify the schema version in Advanced Installer? If not, might it be added in a future version?
FOLLOW US
Get the latest news in Application Packaging