Admin Studio Exec Conditions
Hi all,
When running custom actions you can set them to run at certain points with certain conditions,
I know REMOVE="ALL" will only run on uninstall and apparently REMOVE<>"ALL" is meant to run only on install.. if im wrong so far please inform me!
I have packaged one app, and it calls back to the msi for some current user registry settings it also runs the few custom actions i have running, i would like to stop my custom actions running when this occurs and for them to only occur on a brand new installation.
If that makes no sense please say so :)
When running custom actions you can set them to run at certain points with certain conditions,
I know REMOVE="ALL" will only run on uninstall and apparently REMOVE<>"ALL" is meant to run only on install.. if im wrong so far please inform me!
I have packaged one app, and it calls back to the msi for some current user registry settings it also runs the few custom actions i have running, i would like to stop my custom actions running when this occurs and for them to only occur on a brand new installation.
If that makes no sense please say so :)
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
TomB
18 years ago
Ryath,
If you want your CA to only run on when the package is installed and NOT on a repair or removal then you should use the condition NOT Installed.
If you want your CA to only run on when the package is installed and NOT on a repair or removal then you should use the condition NOT Installed.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.