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 table, but I don't define
any InstallUISequence in my .wxs.
In a verbose log, I can see that the MigrateFeatureStates action is
executed, and the features are set to the right state.
What could be wrong?
Thank you.
Eric Prévost
Le 2013-02-20 16:55, Eric Prévost-Dansereau a écrit :
> 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")=or
> Session.FeatureCurrentState("Feature")=
>
> This works fine for new install, repair, and modify.
>
> However, on a major upgrade, FeatureRequestState returns -1 and
> FeatureCurrentState return 2. Il know that the features are actually
> migrated, because the files related to each features are installed.
>
> My MajorUpgrade element is defined like this:
>
> <MajorUpgrade AllowSameVersionUpgrades=o" MigrateFeatures="yes"
> DowngradeErrorMessage=nstalled version is newer." />
>
> How can I check if a feature has been migrated on a major upgrade in
> vb script? Currently, my custom action is scheduled to run after
> InstallFinalize.
>
>
> Thank you.
>
> Eric Prévost
>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
