Phil wrote:
> Or a slightly modified version of this could be that the user's installed
> shortcut simply points to a "boot-strap" program which checks an ini file
> for which executable to run and launches that program. New updates simply
> modify the ini file to point to the latest exe. You would have to
> go though
> and clean out old executables at a later date when you are sure no-one is
> running them.
Yes, that's pretty what we do with LaunchGuard. The app shortcut points to
LaunchGuard along with parameters to indicate how it should 'function'. Once
you have a "bootstrap" program like you suggest, you can pretty much do what
you like.
> You could even have the executables themselves check the ini file
> and give a
> message such as "a newer version of this program is available,
> please close
> down this application and restart it to run the latest version".
Like in an idle-timer? Yes, I suppose you could do that. Still updates would
have to be pretty damn frequent for that to buy your users much.
Mind you, our _testers_ might appreciate it in-house so they know to recheck
their pending defects. Hrmm.. I might ask them about that. Thanks for the
suggestion!
TTFN,
Paul.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
