I've reviewed both Doug's and Nick's applauncher files but want to ask some general questions about app launchers at the risk of asking the obvious.

Typing out loud here.....

---------

Lets say my 'real' EXE is called MY.EXE. The launcher exe is called LAUNCHMY.EXE.

During the FIRSTTIME app install, i would want to install:

- MY.EXE into "MyApp\Source" folder (granted it could be anything)
- LAUNCHMY.EXE into "MyApp\LatestExe" folder.

Any future releases of the program get installed into the "MyApp\LatestExe" folder (including other files like the DBC files, new DBFs, SDT stuff, help files, ...).

Instead of the users running MY.EXE, they run LAUNCHMY.EXE instead. So installshield needs to build an app icon for LAUNCHMY.EXE instead.

When LAUNCHMY.EXE is run, it compares the following 2 files (maybe others):

MyApp\Source\MY.EXE
MyApp\LatestExe\MY.EXE

and copies the newer files from the "MyApp\LatestExe" folder to the "MyApp\Source" folder. And finally, LAUNCHMY.EXE runs MY.EXE.

=========
Questions
=========
1) are there any SDT issues with this setup?
2) is there a way to prevent users from running MY.EXE when they should be running LAUNCHMY.EXE instead? Can the program stack be checked?
3) what performance improvements are common when users have the EXE local on their drive?
4) if a user is running LAUNCHMY.EXE (which runs MY.EXE), does the "START IN" value of the program shortcut suffice for "locating" the user to the correct path?