Bob, what was the 'normal' custom action that you used at the end of the
install to launch your app with arguments?
I was also using LaunchApplication to trigger the launch of my application
at the end of the UI by check box selection, but I also needed to supply
arguments and therefore it did not
Thanks! Got it working.
Bob Arnson-6 wrote:
>
> chaiguy1337 wrote:
>> Is there a particular reason the example in the help file didn't use
>> "normal"
>> exe custom actions? I don't want to do something that might cause
>> problems
>> later.
>>
>
> Because a more typical use case is to laun
I wasn't talking about launching another install, I was talking about
launching the application that was just installed. I guess that makes sense
as to why ShellExec was chosen for the example. I will fiddle around with
normal custom actions and see if I can get it working.
Bob Arnson-6 wrote:
>
chaiguy1337 wrote:
> Is there a particular reason the example in the help file didn't use "normal"
> exe custom actions? I don't want to do something that might cause problems
> later.
>
Because a more typical use case is to launch a document (like a
readme.html or .pdf). WixShellExec was desi
Is there a particular reason the example in the help file didn't use "normal"
exe custom actions? I don't want to do something that might cause problems
later.
Bob Arnson-6 wrote:
>
> chaiguy1337 wrote:
>> Hi all. I'm looking for a way to pass command line arguments to my app
>> launched when t
chaiguy1337 wrote:
> Hi all. I'm looking for a way to pass command line arguments to my app
> launched when the installation is complete, so that my app knows it was
> launched by the installer.
>
> I basically copied the example from the help file:
>
>Value="[#OrangeNote.exe]" />
>
6 matches
Mail list logo
