Conditions of Custom Actions Used in MSI

As far as I can see, there's a mistake in Condition No. 3:

To let an action run during install and remove, you can not set the condition to NOT REMOVE (as it won't run during remove that way).
However, an action with this condition will run on install and [b]repair[/b].

Apart from above mention condition there can be user defined condition. Example Any user defined PUBLIC property can be a condition over Custom Action. Example if packager set a Property using APPSearch Table / System Search. This can be set as a property for custom Action.

One more thing like to add is in condition 8, I guess there is a Typo error, it should be
REMOVE~="All"
as ~= is used for case sensitivity not =~

Immediate

 Custom actions, can be sequenced anywhere within any of the sequence tables
 Custom actions have access to the Installation database
 Custom actions can only run in the User Context
 Custom actions should never modify the system state. i.e. should not run in elevated context

Deferred

 Custom actions can be sequenced only between the InstallInitialize and InstallFinalize actions in the sequence tables
 Custom actions doesn’t have access to the Installation database
 Custom actions can run both in the context of the user and elevated using the system context.
 Custom actions can modify the system state.i.e can be run in elevated context.

Hi,

I have 2 update patches for my setup. I want a custom action to run during the first time install and during Patch01. But if Patch01 is already installed I don't want the custom action to run during the Patch02. What would the condition be?

Thanks

Can you please elaborate what are "$" sign used for in the Condition of Custom Actions. We can see these in Custom Actions of Vendor MSI.

Thanks

I came across one more condition which might be helpful to all.

If you want your CA to run only if it is upgrading a previous version then you can put the UPGRADE_1 (Upgrade property) in the condition.

Hope this is helpful.