So first of all, it appears there is no support for this product anymore.
Is that correct?
The issue I'm having might be handled by someone familiar with MSI, anyway.
The issue is that I have two installers, one for the "light" version of my
product, one for the "full" version. One of the files that is different
between the two versions, has the same name in each version, but a different
version number. The problem is that when I install a full version on top of
an existing light version, that file doesn't get replaced. I've tried a
variety of different version numbers for this file, it doesn't seem to
matter what version numbers I give the file, it never gets updated.
I can pass command line flags from InstallShield into Windows MSI and I'm
passing
/l*v a.log
and there is nothing in the log file that indicates it's even considering
the version #s of the two files (the one on the disk, and the one in the
installer).
So my questions ...
1) Are there better command line flags for me to use, so I can see it
considering the version #s?
2) Which version #s does it use to decide whether the file on the disk or
the file in the installer is newer? The file is an executable created using
Visual Studio 6, so I can set the FILEVERSION, PRODUCTVERSION, FileVersion,
and ProductVersion.
Thanks,
Chris
It seems to me that the full version should be a major upgrade that replaces
the light version.
--
Phil Wilson
"Chris Shearer Cooper" <chri...@sc3.net> wrote in message
news:x-2dnepmsobaG4LVnZ2dnUVZ_qSonZ2d@friiip...
I have no idea whether these are reasonable values or not.
Thanks!
Chris
"Phil Wilson" <pdjw...@nospam.cox.net> wrote in message
news:%23rx8vt4...@TK2MSFTNGP05.phx.gbl...
If full is supposed to update light, full needs a higher version, different
ProductCode, same UpgradeCode, new PackageCode, and upgrade entries to
detect and upgrade from light to full.
--
Phil Wilson
Definitive Guide to Windows Installer
http://www.apress.com/book/view/1590592972
"Chris Shearer Cooper" <chri...@sc3.net> wrote in message
news:h-udnW8sZKSWNL3VnZ2dnUVZ_sKqnZ2d@friiip...