Richard
As per the tutorial, my custom action is defined as:
<CustomAction Id='LaunchFile' FileKey='DA_exe' ExeCommand=''
Return="asyncNoWait" />
This yields a custom action of type 210.
I am very curious how your experiment turns out.
John
On 8/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
> Hi John,
>
>
>
> That's odd that ProcessMonitor doesn't even show a failed attempt at
> accessing the file. I would certainly expect **something** to show up.
>
>
>
> Assuming you're following the tutorial example, I believe what should be
> getting triggered is a type 18 custom action. Since you haven't mentioned
> otherwise, I also assume that there are no parameters being passed (i.e.
> the ExeCommand attribute is present, but empty). Is that correct?
>
>
>
> It is certainly possible that the path to the executable is not being
> resolved properly, although if that were the case I would expect people to
> have reported it as a bug long ago. I'm waiting for a build to finish, so
> I'm going to see if I can get a minimal example working and try to reproduce
> the problem here.
>
>
>
> Regards,
>
> Richard
>
>
> ------------------------------
>
> *From:* John Lalande [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, August 09, 2007 12:54 PM
> *To:* Foster, Richard - PAL
> *Cc:* wix-users@lists.sourceforge.net
> *Subject:* Re: [WiX-users] Run program after installation
>
>
>
> According to the tutorial, the FileKey attribute of the custom attribute
> is set to the Id of the file you wish to run so I assume that it is trying
> to run the executable directly...which I also successfully tested.
>
> But I don't really know the exact command that the installer is calling as
> it isn't being logged. Using the ProcessMonitor does not show the program
> getting run if I change the installation directory during the install.
>
> However, I did do an experiment where I set the installation folder on the
> command line by setting INSTALLDIR to what is not defaulted in the
> installer. At the end of the install, the program started when the checkbox
> was set. This leads me to believe that the path to the executable is being
> resolved very early and subsequent changes are not being reflected in the
> custom action.
>
> You are certainly right about this being commonly implemented
> functionality.
>
> Thanks again
>
> John
>
> On 8/9/07, [EMAIL PROTECTED] <
> [EMAIL PROTECTED]> wrote:
>
> John,
>
>
>
> Be careful - Running from the shortcut may not be a completely valid test.
> You really need to launch it (e.g. using Start / Run) using exactly the
> same command line as Microsoft Installer will.
>
>
>
> You may want to try running the installation with ProcessMonitor running
> (you can get that from
> http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspxif
> you haven't encountered it before – although I haven't tried the version
> that was apparently released yesterday!). That will show you exactly what
> file(s) are being accessed etc. and may provide some hints about what is
> going wrong.
>
>
>
> What you are trying to accomplish is common enough that I think there
> would be a lot more traffic about it on the list if the tutorial was badly
> wrong. (As I said, I have used that mechanism myself to launch "readme"
> files with no trouble.)
>
>
>
> Hope you manage to get it resolved.
>
>
>
> Regards,
>
> Richard
>
>
> ------------------------------
>
> *From:* John Lalande [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, August 09, 2007 11:18 AM
> *To:* Foster, Richard - PAL
> *Cc:* wix-users@lists.sourceforge.net
> *Subject:* Re: [WiX-users] Run program after installation
>
>
>
> Richard
>
> It certainly is not a silly question and was worth checking. I checked
> and the program does not depend on its location. If I install to a
> non-default folder I can run the program from its shortcut.
>
> I am starting to think that perhaps this cannot be done as easily as the
> tutorial illustrates.
>
> Thanks for your response.
>
> John
>
> Richard wrote:
> >It may be a silly question (and hopefully is), but does the application
> >itself have any path-related dependencies? I.e. can you use the same
> >command line as Installer would use successfully, bearing in mind that
> >the working directory and the application's installation directory may
> >not be the same. I haven't launched an installed application using the
> >mechanism described, but I have triggered the opening of a specific file
> >from the location it was installed to without any trouble.
> ------------------------------
>
>
> * C O N F I D E N T I A L I T Y N O T I C E *
> -----------------------------------------------------------
> The content of this e-mail is intended solely for the use of the
> individual or entity to whom it is addressed. If you have received this
> communication in error, be aware that forwarding it, copying it, or in any
> way disclosing its content to any other person, is strictly prohibited.
> Quixote Traffic Corporation is neither liable for the contents, nor for the
> proper, complete and timely transmission of (the information contained in)
> this communication. If you have received this communication in error, please
> notify the author by replying to this e-mail immediately and delete the
> material from any computer.
>
>
>
> ------------------------------
>
> * C O N F I D E N T I A L I T Y N O T I C E *
> -----------------------------------------------------------
> The content of this e-mail is intended solely for the use of the
> individual or entity to whom it is addressed. If you have received this
> communication in error, be aware that forwarding it, copying it, or in any
> way disclosing its content to any other person, is strictly prohibited.
> Quixote Traffic Corporation is neither liable for the contents, nor for the
> proper, complete and timely transmission of (the information contained in)
> this communication. If you have received this communication in error, please
> notify the author by replying to this e-mail immediately and delete the
> material from any computer.
>
>
-------------------------------------------------------------------------
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-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
