Hi!
I have a custom action, which is deferred and defined to be executed after InstallFiles when this
NOT(UPGRADINGPRODUCTCODE)
condition is met.
But as I can see, even during upgrade, this action is executed? Why?
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Custom Action is always executed despite condtion
Started by
TomekR
, Sep 24 2010 10:09
3 replies to this topic
Posted 24 September 2010 - 11:37
Check the log file. Note that UPGRADINGPRODUCTCODE is only set for the old MSI which is being removed by the major upgrade, not in the new version which is being installed. And it requires MSI 4.0 or higher.
Stefan Krüger
InstallSite.org twitter facebook
Posted 24 September 2010 - 12:57
QUOTE (Stefan Krueger @ 2010-09-24 11:37) |
Check the log file. Note that UPGRADINGPRODUCTCODE is only set for the old MSI which is being removed by the major upgrade, not in the new version which is being installed. And it requires MSI 4.0 or higher. |
If I got you right, Stefan, upgrade with Windows installer looks like this:
1. old product version is being removed.
To do this, old MSI (the one which installed old version) is being used and UPGRADINGPRODUCTCODE is set
2. new version is being installed
new MSI is being used and UPGRADINGPRODUCTCODE is not set.
Thank you for your explanation!
Posted 27 September 2010 - 18:32
Yes, that's correct (for a Major Upgrade). Note however that the order of events depends on the sequencing of the RemoveExistingProducts action.
Stefan Krüger
InstallSite.org twitter facebook