Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
How to manage .exe updates?
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00856274
Message ID:
00856278
Vues:
14
>Hello everyone,
>
>I am gradually rewriting a huge Foxpro/DOS application in VFP 7.0 while it is actively in use by about 55 users. I have my Installshield setup configured to place the EXE on the local hard drive, and all the data is read from the network drive.
>
>I would like to automate a way to flag the user if there is an update to the version of the EXE on thier local drive, and give them the option to update it immediately.
>
>I'm not sure how an updated version number affects an install/update of an existing program, etc...
>
>I am reading up on using version #s in my exe, but if anyone can point me in the right direction I'd appreciate it.
>
>Thanks in advance,
>Larry Morelli


Hi Larry,

I use 2 ways to achieve this.

First is launching the application with the launcher program that first checks if there is a newer version of the EXE in a specified directory on the network and, if so, copies it to the local workstation. (EXEs always run from the local copy). The launcher app itself resides on the network. So, when the user restarts the app, s/he may be sure that the latest version is run. That takes care of application updates.

Second, if by whatever reason you need to kick all users out (distribute new version of DBC, do the table reindexing, etc.), there is a timer in the EXE that checks every minute if there is a certain file (for example, called SHUTDOWN.TXT) somewhere on the network (say, in application data directory) and if it sees the file, it puts the warning message up and shuts down the app, say within 30 seconds. If the user is not there, it can even make an educated guess :) and save or cancel opened data editing sessions if the user is not there. The exact logic here depends on your application.

My apps, for example, can prevent logging in new users, allowing to continue working those who already logged in. They may kick out all users (with the file SHUTDOWN.TXT)or selected ones with the file [USERLOGINNAME].TXT

You can find my Launcher (file#9668) in Downloads section, as well as other submissions of that kind.
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro

"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform