Hi Bob,
the package runs from the User Temp directory. The package code is
changed. I think there are two problems:
one - ADDLOCAL is not looking as expected when doing a typical
install because it's set to everything. But the typical
setup will actually install what I want. Maybe it's again some property
update which takes place after a certain action.
Please clarify this.
Here is the log on a typical install:
Action start 10:00:19: ExecuteAction.
MSI (c) (F8:20) [10:00:19:859]: PROPERTY CHANGE: Adding SECONDSEQUENCE
property. Its value is '1'.
MSI (c) (F8:20) [10:00:19:859]: Grabbed execution mutex.
MSI (c) (F8:20) [10:00:19:859]: Incrementing counter to disable
shutdown. Counter after increment: 0
MSI (c) (F8:20) [10:00:19:859]: Switching to server: CLIENTUILEVEL="0"
CLIENTPROCESSID="3576"
SOURCEDIR="K:\DIS\adm\bin\Win_pkgs\rtm\src\bin\3.1.7\" ACTION="INSTALL"
EXECUTEACTION="INSTALL" SETUPTYPE="Typical" ROOTDRIVE="E:\"
INSTALLLEVEL="1" SECONDSEQUENCE="1"
ADDLOCAL=Administration,Demos,Utilities
It should be only Administration because the setup resets the level
of all other features to 0 when "Typical" is selected like this:
<Feature Id="Utilities" Title="Utilities" Display="1" Level="1"
AllowAdvertise="no">
<Condition Level="0"><![CDATA[SETUPTYPE = "Typical"]]></Condition>
The second is that this ADDLOCAL property is stored somewhere (don't
think it's in the registry because RegMon does not show anything) and
when the update comes in, it will
run with ADDLOCAL=Administration,Demos,Utilities. I tried to change
ADDLOCAL after MigrateFeatureStates with a custom action, but
it remains "Administration,Demos,Utilities" when ExecuteAction is called.
Best regards,
Calin
Bob Arnson wrote:
> Please keep /wix-users/ on the thread.
>
> Calin Iaru wrote:
>> you're right. Now I need to find what is the cause of this
>> problem. I always change the version and product code
>> but somehow I get this message:
>> MSI (s) (14:48) [17:39:13:796]: Skipping RemoveExistingProducts
>> action: current configuration is maintenance mode or an uninstall
> Do you also change package code? Elsewhere in the log, MSI reports
> which .msi package is actually running; if it's under
> %windir%\Installer, it's using an already-installed package.
>
> --
> sig://boB
> http://bobs.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
