MSI and AMUS/OMUS/ VAMUS and File Over-Writing (Possible Solution)

  • Thread starter Thread starter Martyn Jones
  • Start date Start date
M

Martyn Jones

Hi All

I thought I'd share this information with you as it appears to be a
serious topic for discussion. Basically I had the problem whereby
Install Shield(MSI's) was not correctly updating files without version
numbers even though I have experimented with ReInstallMode settings of
AMUS, OMUS & VAMUS.

Below is an Extract from Install Shield which has resolved the issue
for me. I hope it does the same for you.

----------------------------------------------------------------

Extract:

The source of the behaviour may stem from Microsoft file versioning
rules. If the target machine contains a file with a newer modified
date then the behaviour would be expected. In most cases the
behaviour can be workaround using a feature contained in the DevStudio
9 product. The Windows Installer service will allow a ‘version'
attribute to be assigned to a component. Microsoft file versioning
rules state that a versioned file will overwrite a non versioned file
regardless of the modified or created dates. To use this feature right
click on the file and select Properties Next Check the Override system
version and place a value into the edit field (1.00.0000). Build a new
release and test for similar behaviour.
 
Back
Top