I've encountered lately some very strange behavior on an Install Shield basic msi project. Shortly I want rename a file and to modify its content after copied locally but only when cetain condition is met. To do this I've wrote a 2 deferred VB custom actions and set the condition. The problem is that it seems the condition is evaluated twice and I don't know why. Let's say the condition is "IS_MAJOR_UPGRADE". The scripts should ran only when the condition is false. Presuming the installation is a Major Upgrade, looking in the log I found that at first the "IS_MAJOR_UPGRADE" property is set to "yes". Looking at my CA's they are marked to not be run do to condition "true" at the first evaluation step. But later the "IS_MAJOR_UPGRADE" property is evaluated again and it has no value this time so the condition is evaluated as "false" and my CA's are executed. Can someone expalin to me why is "IS_MAJOR_UPGRADE" property evaluated twice? And why, in case of deferred action, the execution condition evaluation is done twice?
As far as I know property is evaluated twice because first time it’s in the UI Sequence and second time is in the Execute Sequence. Try to add your property to the SecureCustomProperties list.
