Changing value in InstallExecuteSequence Bala <balakrishna.bk[ at ]gmail.com> 05.07.2007 11:10:36 Hi, I am newbie to msi technology and I have the following question in InstallExecutesequence. I am editing my existing msi file using orca and want to swap sequence numbers of appsearch and launchcondion actual Appsearch = 400 as sequence number and Launchcondition = 117 I added a new entry in Reglocator, apsearch and launchcondition and swapped the sequence numbers. So, after modifying my new entry is Appsearch = 117 launchcondition = 400 When i save and launch this msi, i still get launch condition executed 1st in the sequence and installation fails inspite of have regkey in the system Do I need to change this sequence number in each of the language specific msi (extract mst, apply, change, and create msi)..? or modifying the final one is sufficient Thanks, Bala.

Re: Changing value in InstallExecuteSequence mike[ at ]dimmick.demon.co.uk (Mike Dimmick) 05.07.2007 18:07:42 Windows Installer executes the actions in the order specified in the sequences. However, when installing using Full or Reduced UI, it begins by executing the InstallUISequence, not the InstallExecuteSequence. You have to have some actions duplicated in both sequences in case the user opts for Basic or No UI, in which case the InstallUISequence is skipped. You have to schedule the ExecuteAction action in the UI sequence to transfer control to the InstallExecuteSequence. Another option, to keep the predefined sequences, is to use a Type 19 Custom Action to display an error message if the AppSearch doesn't find the required information, and schedule that action after AppSearch (in both UI and Execute sequences, to cover the Basic/No UI case). You need to invert the condition compared to using a LaunchCondition: LaunchCondition produces the error if the condition is false, while the CustomAction is run if the condition is true. -- Mike Dimmick