RE: [WiX-users] "...file versioning rules would disable the component"

[Ross Anderson]

Thanks for the quick answer, Chris.  Unfortunately, no – the Attributes column for the file is 0.  The file is a sql server .mdf file.  So it doesn’t contain any checksum or versioning information (as far as windows installer should be concerned).  If I cause a reinstall before the file is modified, I get the following output:   Disallowing installation of component: {846A216C-4DD7-4B6E-A1B5-1B7A222D6071} since the same component with higher versioned keyfile exists   After the file is modified, I get the output I posted below.   Scanning the log file, other than the REINSTALLMODE property, I couldn’t find anything else that suggested why this might be happening.  Very confusing.   Ross   From: Christopher Painter [mailto:[EMAIL PROTECTED] Sent: Thursday, June 01, 2006 9:54 AM To: Ross Anderson; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] "...file versioning rules would disable the component"   You said pocmus.  C is: Verify the checksum values, and reinstall the file if they are missing or corrupt. This flag only repairs files that have msidbFileAttributesChecksum in the Attributes column of the File Table. So I'm guessing you have the msidbFileAttributesChecksum attribute set for your key file, so even though the file is modified and default file versioing rule of omus would disallow the component the C tells it to respect that the hash is incorrect and reinstall it. Just a quick guess... Chris Ross Anderson <[EMAIL PROTECTED]> wrote: Hi,   Apologies if this is more msi than wix, but this group is a lot more active than platformsdk.msi, and people seem to get away with asking a few non-wix specific questions here…   I have a question about a reinstall triggered by an advertised shortcut.  Looking at the log file, the reinstall is triggered with REINSTALLMODE=pocmus.   One of the components in my package has an unversioned file as the keyfile.  During the reinstall, the following line is output to the log:   Allowing installation of component: {846A216C-4DD7-4B6E-A1B5-1B7A222D6071} even though a modified unversioned keyfile exists and file versioning rules would disable the component   I do not want the file to be reinstalled if the file already on the system is modified - I want the installer to follow the versioning rules.  Why is it choosing NOT to follow them?  Google didn’t turn up anything of interest, and the msi documentation didn’t clear it up for me either.   Thanks!   Ross     How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call rates.