We are hitting this more frequently. By the way, the error message saying about
webDir, but we only use webVirtualDir element in the authoring.
- Original Message -
From: Zhisheng Huang
To: Zhisheng Huang ; John Cooper
; General discussion for Windows Installer XML toolset.
; General
If you are strictly following the component rules, consider that during
Major Upgrades with late scheduling of RemoveExistingProducts the following
scenarios hold:
- Upgraded components will be installed without removal of the obsoleted
version of those components.
- Unchanged components will be i
The WiX documentation itself has a page on logging:
How To Guides\Others\Get a log of your installation for debugging
The online version of that page is here:
http://wix.sourceforge.net/manual-wix3/get_a_log.htm
It is instructive to read the logs sequentially as it allows you to see the
flow tha
You cannot make a new MSI file with a new ProductCode, run it and expect that
it will just update your existing files. You've changed the ProductCode, making
it a completely different product so yes you get two entries in ARP.
The other replies cover this anyway, but if you go the major upgrade
Hi,
I've created an MSM project which executes a Custom Action.. however
having hooked the MSM into a Setup project, during the installation if
fails with the following error...
CustomAction RegisterAddIn returned actual error code 1154 (note
this may not be 100% accurate if translation hap
The simplest way to implement a major upgrade is, as you say, put * for
product code, keep the upgrade code and increment the product version. Then
just add:
That automatically adds the RemoveExistingProducts action and the appropriate
Upgrade table entries and prevents downgrades too.
-Ori
6 matches
Mail list logo
