how do I start up an external application at the end of my installation ?

  • Thread starter Thread starter Flemming Knudsen
  • Start date Start date
F

Flemming Knudsen

I need to start up an external application when my own installation is
finished - the application is present in a sub-directory next to the
MSI-file.

I also need to be able to display an readme.txt file ... I have tried to add
some 'custom actions' for it but without result.
 
The Windows Installer documentation on MSDN provides information on how to
launch a file at the end of the installation. Consult the topic "How do I use a
custom action to launch an installed file at the end of installation?" at <
http://msdn.microsoft.com/library/d...alled_file_at_the_end_of_the_installation.asp
. The Windows Installer SDK available at <
Click to expand...
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ > provides sample
code for the custom action that accomplishes this.

Hope this helps,
- Carolyn Napier
Microsoft Windows Installer Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
MSI FAQ:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx>
 
you are right - if it is an installed file - what if the file isn't
installed but located next to the msi-file ?
 
So this file is present at the installation source location and not actually
installed during installation? There are a number of different custom action
types as documented in the Windows Installer documentation on MSDN. Try <
http://msdn.microsoft.com/library/d...p/summary_list_of_all_custom_action_types.asp >
for the summary list.

A lot depends on the type of file to launch, but given this is an application
we'll go with EXE. In general, I would suggest looking at a type 50 custom
action which you use a property to indicate the source location for the package
(SourceDir is good on initial install). Alternatively, you can embed the
executable directly in the Binary table of the MSI package and use a type 2
custom action to launch it. More information on the individual custom action
types can be found on MSDN.

I generally recommend avoiding launching custom actions from the install source
location -- particularly if you don't conditionalize so they don't launch
outside of original installation. If the user doesn't have access to the source
(perhaps s/he isn't connected to the network), the install can fail because it
can't run the custom action.

Hope this helps,
- Carolyn Napier
Microsoft Windows Installer Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
MSI FAQ:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx>
 
Back
Top