Hi Michael,
There are a few methods to execute a file using a custom action. Basically,
it depends whether you are deploying the file, have it on the binary table,
or the file already exists. According to your email, you are deploying the
file with your installation. Therefore, the simplest approach is to use the
FileKey attribute in the custom action to reference to your file. Also, you
must schedule the ca after the files are copied, i.e.
After="InstallFinalize". See below: - I tested this on my machine to be sure
it works :^)
<Directory Id="TARGETDIR" Name="SourceDir">
<Directory Id="ProgramFilesFolder" Name="ProgramFilesFolder">
<Directory Id="INSTALLDIR" Name="product">
<Component Id="Notepad2" Guid="*">
<File Id="Notepad2" Source="
C:\bin\Notepad2\Notepad2.exe" />
</Component>
</Directory>
</Directory>
</Directory>
<CustomAction Id="Notepad2" Execute="immediate" Return="asyncNoWait" FileKey
="Notepad2" ExeCommand=""/>
<InstallExecuteSequence>
<Custom Action="Notepad2" After="InstallFinalize">Not REMOVE</Custom>
</InstallExecuteSequence>
<Feature Id="Complete" Title="Application Name" TypicalDefault="install"
Display="expand" Level="1">
<ComponentRef Id="Notepad2" />
</Feature>
On Sun, Nov 23, 2008 at 9:45 PM, cemiles <[EMAIL PROTECTED]> wrote:
>
> ...
>
> <CustomAction Id="LaunchNotepadExe" Execute="immediate"
> FileKey="Notepad.exe" Return="asyncNoWait"
> ExeCommand='"[INSTALLDIR]Notepad.exe"' />
>
> <Custom Action="LaunchNotepadExe" After="InstallFinalize"></Custom>
>
>
> Love88Keys wrote:
> >
> > I´ve read part of Wix-Tutorial "http://www.tramontana.co.hu/wix.."; about
> > how to start an exe-file which is already installed on the system. The
> > suggested solution was:
> >
> > <Property Id='NOTEPAD'>Notepad.exe</Property>
> > <CustomAction Id='LaunchFile' Property='NOTEPAD'
> > ExeCommand='[SourceDir]Readme.txt' Return='asyncNoWait' />
> >
> > How can I make to to run an exe which is alredy installed but lies inside
> > my INSTALLDIR. Might be useful: My Action should only tun while
> uninstall.
> > I´ve already done the work for this.
> >
> > Here´s ehat I meant (Of course it doesn´t work):
> > <Property Id='MYEXE'>[INSTALLDIR]MyExe.exe</Property>
> > <CustomAction Id='LaunchFile' Property='MYEXE' ExeCommand=''
> > Return='asyncNoWait' />
> >
> > Thank you, Michael
> >
>
> --
> View this message in context:
> http://n2.nabble.com/Custom-Action---start-exe-inside-my-INSTALLDIR-tp1568179p1569421.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
