It is in the same link. Go to 3.2 Extra Actions you will find it. There are many other standard actions available but not scheduled by default. ScheduleReboot, for instance, will instruct the user to reboot after the installation:
<InstallExecuteSequence> <ScheduleReboot After='InstallFinalize' /> </InstallExecuteSequence> If the need to reboot depends on a condition (for instance, the operating system the installer is running on), use a condition: <InstallExecuteSequence> <ScheduleReboot After='InstallFinalize'>Version9X</ScheduleReboot> </InstallExecuteSequence> It's not only these so-called standard actions that you can schedule and re-schedule. There are a couple of custom actions as well (custom here means that they don't appear in the standard course of events but you can use them wherever and whenever you like). A very common need is to launch the application you've just installed. Custom actions need to be mentioned in two places in the source file. First as a child of the Product tag (for instance, between the closing Feature and the UI tag). This CustomAction tag will specify what to do. To launch an executable we've just installed, refer to it using the Id identifier of the File tag specifying the file. You also have to provide a command line, although it can be left empty if not needed: <CustomAction Id='LaunchFile' FileKey='FoobarEXE' ExeCommand='' Return='asyncNoWait' /> Second, we have to schedule the action the usual way. The link between the action and the scheduling entry is provided by the matching Id—Action attribute pair. If the execution of the custom action is conditional, we can specify the condition inside the Custom tag. We need the condition here so that we only launch the executable when we make an installation but not when we remove the product: <InstallExecuteSequence> ... <Custom Action='LaunchFile' After='InstallFinalize'>NOT Installed</Custom> </InstallExecuteSequence> In some cases, we want to start a helper utility we carry along in the installation package but we don't install on the user's machine (for instance, a readme file viewer or a special configuration utility). Instead of the File, we refer to the identifier in a Binary tag. The scheduling is the same: <CustomAction Id='LaunchFile' BinaryKey='FoobarEXE' ExeCommand='' Return='asyncNoWait' /> We can also launch any other executable on the user's machine if we provide its name in a property: <Property Id='NOTEPAD'>Notepad.exe</Property> <CustomAction Id='LaunchFile' Property='NOTEPAD' ExeCommand='[SourceDir]Readme.txt' Return='asyncNoWait' /> hina1703 wrote: > > Thanks Matthew. Which tutorial are you refering to? I am going through > http://www.tramontana.co.hu/wix/index.php#TOC tutorial. > > Hina > > > Matthew Janulewicz-2 wrote: >> >> I have found that I sometimes have some luck installing non-Windows >> Installer based installs without using a bootstrapper. I've had luck >> with InstallShield packages because (I think) it uses it's own engine. >> (I was just doing this with CuteFTP yesterday, in fact.) I'm not sure >> what packager Adobe Reader uses, but it might be worth just trying it. >> >> --- >> >> You'll need to use a custom action and then trigger it. As an example: >> >> 1. Add your second installer as a binary reference: >> >> <Binary Id="CuteFTP_EXE" SourceFile="Assets\cuteftppro8.exe" /> >> >> 2. Set up a custom action for it: >> >> <CustomAction Id="Launch_CuteFTP_Installer" BinaryKey="CuteFTP_EXE" >> ExeCommand="" Return="asyncWait" /> >> >> 3. Set the custom action to run at some point. I have mine hooked up to >> a button on a dialog: >> >> <Control Type="PushButton" Width="70" Height="17" X="90" Y="117" >> Id="InstallCuteFTP" Text="Install CuteFTP"> >> <Publish Event="DoAction" Value="Launch_CuteFTP_Installer" /> >> </Control> >> >> You might also sequence it after InstallFinalize. It's up to you. >> >> 'The Tutorial' has much information on launching external apps. >> >> >> -Matt >> >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson >> Sent: Wednesday, October 10, 2007 9:03 PM >> To: hina1703 >> Cc: wix-devs@lists.sourceforge.net >> Subject: Re: [WiX-devs] How to launch a third party executable >> duringinstall? >> >> hina1703 wrote: >>> Can you please give an example? I am trying to install adobe reader >> during an >>> install: >>> >> >> You won't be able to install Adobe Reader because you can't install two >> products simultaneously. You need to use a chainer, or, better yet, give >> >> the user a choice of PDF reader. >> >> -- >> sig://boB >> http://joyofsetup.com/ >> >> >> >> ------------------------------------------------------------------------ >> - >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> WiX-devs mailing list >> WiX-devs@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-devs >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> WiX-devs mailing list >> WiX-devs@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-devs >> >> > > -- View this message in context: http://www.nabble.com/Re%3A-How-to-launch-a-third-party-executable-duringinstall--tf4608490.html#a13164844 Sent from the wix-devs mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
