om: AG Crum [mailto:crum.and...@gmail.com]
> Sent: Friday, May 29, 2009 7:42 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] EmbeddedUI Install Execute Sequence
>
> I've noticed that if you are using an EmbeddedUI, actions like
> FindRelatedProducts and Launc
ay, May 29, 2009 7:42 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] EmbeddedUI Install Execute Sequence
I've noticed that if you are using an EmbeddedUI, actions like
FindRelatedProducts and LaunchConditions don't work.
The reason is that those actions are sequenced
I've noticed that if you are using an EmbeddedUI, actions like
FindRelatedProducts and LaunchConditions don't work.
The reason is that those actions are sequenced AFTER the embeddedui
initializes. My experience is that you have to do all of your custom UI work
within the scope of Initialize() and
bject: [WiX-users] EmbeddedUI
I'm using the latest build and I have simple Wix project through Votive. I'm
using the sample DTF embedded UI project. I've had this working before, but
now the MSI fails to load anything. The msiexec log starts with this:
SFXCA: Extracting embe
I'm using the latest build and I have simple Wix project through Votive. I'm
using the sample DTF embedded UI project. I've had this working before, but
now the MSI fails to load anything. The msiexec log starts with this:
SFXCA: Extracting embedded UI to temporary directory:
C:\Users\myusernam
I'm using the latest build and I have simple Wix project through Votive. I'm
using the sample DTF embedded UI project. I've had this working before, but
now the MSI fails to load anything. The msiexec log starts with this:
SFXCA: Extracting embedded UI to temporary directory:
C:\Users\myusernam
6 matches
Mail list logo