MSIFILEHASH TABLE
My client has requested not to put any INI entry or .mdb entry in the MSIFILEHASH table , i want to know the reason why we should do this . Is there any specific reason for his request ? Please answer
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
AngelD
17 years ago
The MsiFileHash table is used for unversioned files, thats is files in the File table with a blank Version column.
If the file's hash included in the package differ from the already existing one then the create and/or modified date is used to compare if the file should be replaced or not.
So if they do not want to replace any existing INI or MDB files then adding the msidbComponentAttributesNeverOverwrite bit to the component attribute would prevent to overwrite existing files if the INI or MDB is set to keypath for the component.
If they want to overwrite older or the same (create or modified date) files then using MsiFileHash table would be recommended.
If the file's hash included in the package differ from the already existing one then the create and/or modified date is used to compare if the file should be replaced or not.
So if they do not want to replace any existing INI or MDB files then adding the msidbComponentAttributesNeverOverwrite bit to the component attribute would prevent to overwrite existing files if the INI or MDB is set to keypath for the component.
If they want to overwrite older or the same (create or modified date) files then using MsiFileHash table would be recommended.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
