divo wrote:
> 2. Executing FindRelatedProducts when the Next button is clicked in the
> install scope dialog:
>
It doesn't have to be called in the UI sequence at all. It's scheduled
to run in the execute sequence if not run during the UI sequence. And
that avoids the need to disable the Back
onday, November 03, 2008 7:12 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Why doesn't Windows Installer remove the oldversion in
an upgrade?
Hi,
I am facing the exact same problem, i.e. FindRelatedProducts happens long
before the user is asked to choose the installation sc
Hi,
I found a way to solve the problem:
1. Supressing FindRelatedProducts in the InstallUISequence
2. Executing FindRelatedProducts when the Next button is clicked in the
install scope dialog:
WixAppFolder =
"PerUser"
WixAppFolder =
"PerMachine"
1
3. Disable the Back b
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 Advan
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 w
, adding a
> element setting ALLUSERS fixed my problem.
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Phil
> Wilson
> Sent: Monday, June 12, 2006 8:28 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-
lf Of Phil
Wilson
Sent: Monday, June 12, 2006 8:28 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Why doesn't Windows Installer remove the
oldversion in an upgrade?
Have you looked the log entries for FindRelatedProducts? They should say
something about whether it found the p
7 matches
Mail list logo