#127 Add compiler extension to launch an application after instal

[Robert Flaming]

Here's the VSI way which is wrong

Here are the basic steps to get your application to run.
You need to add a custom action to your setup project.
Just a word of warning, this will not work like the Install
Shield setups where the setup disappears and then the
application starts. This custom action will cause the
application to be run in the commit phase of the install,
which means the last dialog in the setup will still be
showing when the application starts running.

1. Create a .vbs file with the following code.
   Set WshShell = CreateObject("WScript.Shell")
   WshShell.Run """" & Property("CustomActionData")
   & """",7,False
   Set WshShell = Nothing
2. Open your setup project and go to the
   Custom Actions Editor
3. Select the Commit Node and right-click, add
   a new Custom Action
4. Browse the filesystem to add the .vbs file
   from step 1
5. Edit the CustomActionData property and add
   the following:
   [TARGETDIR]YourApp.exe
6. Change “YourApp.exe” to whatever your
   startup app file name is.
   Here is a walkthrough that explains how to create a
   custom action:
   http://msdn.microsoft.com/library/default.asp?
   url=/library/en-
   us/vsintro7/html/vxwlkwalkthroughcreatingcustomaction.
   asp

If you want the application launch to be dependent on
the users input, you will also need to read this
walkthrough on how to pass data to a custom action,
http://msdn.microsoft.com/library/default.asp?
url=/library/en-
us/vsintro7/html/vxwlkwalkthroughcreatingcustomaction.
asp, and modify the above custom action appriopriately.

[Rob Mensching]

Logged In: YES
user_id=991639
Originator: NO

Bob wrote a ShellExecute CusotmAction.