Table Editing Fault

[Alastair]

I have recently needed to add a row to the msiDigitalCertificate table and found that while the msi did build correctly, the new row is lost after the project is saved, closed and reopened.

The procedure to recreate the bug is :-
1 - Sign the project with a certificate to add a row to the msiDigitalCertificate table
2 - Add a second row to the msiDigitalCertificate table using the Advanced Installer table editor to add a second certificate
3 - Save the project
4 - Build the project (this may be an unnecessary step)
5 - Close the project
6 - Open the project. There will now be only one row in the msiDigitalCertificate table instead of the expected two rows.

I am using Advanced installer 7.6.1 because v7.7 does not build patches for us due to a fault reported elsewhere.

Best Wishes,
Alastair

[Bogdan]

Hi Alastair,

I'm afraid we cannot reproduce this behavior on new project. Please note that this table is used only when "Include CAB file into the MSI database" from Media page, Media tab, is not checked.
Is this the case for your project?

Also, have you tried version 8.0.2, or this still presents the problem related to patch creation which you mentioned it exists in 7.7?

Regards,
Bogdan

[Alastair]

Hi Bogdan,

That is most surprising because "Include CAB file into the MSI database" is checked and Orca shows that the msiDigitalCertificate table has been updated in the built msi file as per the edits made in the Advanced Installer table editor. I also edited the msiPatchCertificate table at the same time as editing msiDigitalCertificate - perhaps this step is needed to activate the fault.

We have not tried v8.0.2 yet. If v8.0.2 does not fix the patching problem it looks like we may need to send you our msi, msp and project files, however do you have a standing non-disclosure agreement to assure confidentiality of customer files ? Do you guarantee to destroy customer files as soon as a support call concerning them has closed ?

Thanks,
Alastair

[mihai.petcu]

Hi Alastair,

We don't have a non-disclosure agreement but you can rest to sure we delete all the users' files after they have served their support purpose.
For the confidentiality matter and also for the current case( you are reporting a bug ), I recommend you isolate the issue on a separate project and send that to support at advancedinstaller dot com.
Please do so, this way also assuring the issue is reproduced under the assumed circumstances.

Regards,
Mihai