I did more tests, I found out that the problem occur only when I do a
major upgrade using the parameter /qb on the msiexec command line. If
the installer is launched without the /qb option, my vbscript can get
features' state without any problem.
I understand that /qb skips InstallUISequence ta
Hi,
I have a installer package containing a custom action writing a text
file based on which Features are installed.
Il use the following condition in my vb script to check if a feature is
installed:
Session.FeatureRequestState("Feature")<>2 AND
(Session.FeatureRequestState("Feature")=3 or
S
2 matches
Mail list logo