Hi,
I found a way to solve the problem:
1. Supressing FindRelatedProducts in the InstallUISequence
<InstallUISequence>
<FindRelatedProducts Suppress="yes" />
</InstallUISequence>
2. Executing FindRelatedProducts when the Next button is clicked in the
install scope dialog:
<Control Id="Next" Type="PushButton" X="236" Y="243" Width="56" Height="17"
Default="yes" Text="!(loc.WixUINext)" >
<Publish Property="ALLUSERS" Value="{}">WixAppFolder =
"PerUser"</Publish>
<Publish Property="ALLUSERS" Value="1">WixAppFolder =
"PerMachine"</Publish>
<Publish Event="DoAction" Value="FindRelatedProducts">1</Publish>
</Control>
3. Disable the Back button on the following page, because
FindRelatedProducts is only executed teh first time it is called.
divo wrote:
>
> Hi Bob,
>
> Thanks for your answer, I totally understand that upgrading across
> contexts doesn't make much sense. However, that is not my problem. Maybe I
> wasn't specific enough with my explanation, so here is my scenario (pretty
> much a standard setup scenario IMHO):
>
> The setup is similar to the Advanced setup of Wix 3.0, i.e. it offers a
> page where the user can select whether to install per-user or per-machine
> (like in InstallScopeDlg.wxs in the UIExtension).
>
> 1. ALLUSERS is initially empty, thus per-user is the default
> 2. User installs per-machine by selecting the option in InstallScopeDlg
> (which sets ALLUSERS = 1)
> 3. User updgrades to newer version, the previous version should be
> removed.
> 4. FindRelatedProducts runs before the user makes the selection in
> InstallScopeDlg, i.e. FindRelatedProducts searches for per-user
> installations and ignores the per-machine installation
> 5. User again selects a per-machine setup in the UI.
> 6. The previous per-machine installation will not be removed, although the
> new installation is NOT across context.
>
> The behaviour I would like to have is that FindRelatedProducts runs AFTER
> the user selected the install scope, i.e. step 4 and 5 above should be
> swapped so that in step 6 the previous installation in the SAME context is
> removed.
>
> I guess that this is somehow possible but I don't know how to specify the
> install sequences so that it works (and the WiX compiles).
>
> If anyone could help me with this problem I would be really thankful,
> Best Regards,
> Dirk Vollmar
>
>
> Bob Arnson-6 wrote:
>>
>> divo wrote:
>>> I am facing the exact same problem, i.e. FindRelatedProducts happens
>>> long
>>> before the user is asked to choose the installation scope in the UI.
>>>
>>
>> Generally, the answer is: Don't. It relies on the user choosing the same
>> type of install as the prior version. Major upgrades don't work across
>> contexts.
>>
>> --
>> sig://boB
>> http://joyofsetup.com/
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>
>
--
View this message in context:
http://n2.nabble.com/Re%3A-Why-doesn%27t-Windows-Installer-remove-the-oldversion-in-an-upgrade--tp692400p1454240.html
Sent from the wix-users mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
