How to lauch CA with a feature repair?
Using Advertised Shortcuts with selfhealing works fine, but I like to have more control of the repair by executing e.g. a VBscript or Executable.
Is it remotely possible to execute a Custom Action when a feature repair is triggered?
P.s. I googled the last couple of days but couldn't find any hands-on explanation how to do it. Only a lot people trying to do the same.
Is it remotely possible to execute a Custom Action when a feature repair is triggered?
P.s. I googled the last couple of days but couldn't find any hands-on explanation how to do it. Only a lot people trying to do the same.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
aogilmor
14 years ago
I think what you want is FeatureRequestState which you can find in the msi.chm or online
Posted by:
joseph
14 years ago
I do accept with aogilmor, Below are the some info this helps you.
&
action state of feature
!
installed state of feature
The last four can return the following integer values:
-1
no action to be taken
1
advertised (only for features)
2
not present
3
on the local computer
4
run from the source
A few examples to make things clearer:
(&FeatureName = 3) AND NOT (!FeatureName = 3)
Run action only if the product will be installed locally. Do not run action on a reinstallation.
The term &FeatureName = 3 means the action is to install the feature locally.
The term NOT (!FeatureName = 3) means the feature is not installed locally.
(&FeatureName = 2) AND (!FeatureName = 3)
Run action only if the feature will be uninstalled.
This condition only checks for a transition of the feature from an installed state of local to the absent state.
Thanks,
R.Joseph.
&
action state of feature
!
installed state of feature
The last four can return the following integer values:
-1
no action to be taken
1
advertised (only for features)
2
not present
3
on the local computer
4
run from the source
A few examples to make things clearer:
(&FeatureName = 3) AND NOT (!FeatureName = 3)
Run action only if the product will be installed locally. Do not run action on a reinstallation.
The term &FeatureName = 3 means the action is to install the feature locally.
The term NOT (!FeatureName = 3) means the feature is not installed locally.
(&FeatureName = 2) AND (!FeatureName = 3)
Run action only if the feature will be uninstalled.
This condition only checks for a transition of the feature from an installed state of local to the absent state.
Thanks,
R.Joseph.
Posted by:
thugz888
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.