You should schedule it before LaunchConditions in both the InstallUISequence
(I'm assuming you are using standard MSI UI) and InstallExecuteSequence.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/sequencing-custom-actions-tp5573077p5584163.html
Se
Hi:
I need to sequence a custom action before any launch conditions are checked,
what sequence is the best one to use. This custom action should run whenever
the msi is run.
Cheers
Sean.
--
Start uncovering the many advan
Our application 'MyApp' has two features, one coded in wxs file and other in a
merge module. Both the features are coded with
ConfigurableDirectory="TARGETDIR".
We would like to install the app one directory off of user's choice. We have a
default directory for installation "c:\ProgramFiles
use during deployment
transactions you can't depend on your code being in a useful state.
-Original Message-
From: Armin Linder [mailto:mirram...@googlemail.com]
Sent: Tuesday, October 13, 2009 5:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Sequ
Hi WiX users,
I am seeking advice how I can accomplish the following:
I found out how to sequence custom actions "after InstallFinalize". For my
installation requirements I need a finer degree of control when custom
actions are run, particularily I am seeking for a way to execute a custom
action
Hi.
I have a requirement to run a few custom actions as follows :
1. Sequence a CA to run just before any other file is written or any other
system change is made.
2. Right before the installation starts, launch a custom action to gather
the diffrerent MSI variables, and store them on the registr
6 matches
Mail list logo