>>>I resolved that problem also. My launcher is an EXE and so is my main app. Both are installed locally. The last line in my launcher is RUN /N MyMain.exe followed by a parameter to let MyMain "know" it was started by my launcher exe. If it was not, MyMain will quit. When the user exits out of MyMain, it checks for a new launcher EXE and copies any newer version to the local drive.
>>
>>Interesting. I hadn't thought of doing it that way. Sounds like a good alternative to a server-based launcher.
>
>I had. :) One donwside of this approach is that if you change the Launcher itself, you will have to distribute the new version to user desktops also. Then, to ease the deployment you need the launcher for the launcher and so forth. :)
>In case of the server-side launcher, it can be replaced with a new version on the fly practically anytime, as it may be locked only for a short period of time when it launches the app for one of the users.

What I do is re-write the launcher from the executable when it needs to be modified. It's easy to check too. If the launcher has a time stamp earlier than the executable's internal indicator, re-write.