03-26-2014, 01:50 PM
Is there a way that a locally-running QM-generated exe can check some external condition (eg. whether there is a newer version on a network server) and then if so, pull down the new version and close the version that did the actual check and then start the new version.
Right now, I have this split between two exe's. One (Startup.exe) is in the startup folder. It checks, if new Main.exe version on the server, if not, launch local Main.exe. If new Main.exe version available, Startup.exe pulls down new Main.exe version, then launches "new" Main.exe local version.
Is there a way this can be done by only one installed exe? Once, this Main.exe
The only way I can think of:
1) Main.exe - at launch, pulls down a checking.exe and launches it. The checking exe then checks if Main.exe is up to date, if not, kills it and pulls/down and launches the new one.
I guess this is still two exe's but only requires install of one.
Any thoughts on most elegant way of handling this?
S
Right now, I have this split between two exe's. One (Startup.exe) is in the startup folder. It checks, if new Main.exe version on the server, if not, launch local Main.exe. If new Main.exe version available, Startup.exe pulls down new Main.exe version, then launches "new" Main.exe local version.
Is there a way this can be done by only one installed exe? Once, this Main.exe
The only way I can think of:
1) Main.exe - at launch, pulls down a checking.exe and launches it. The checking exe then checks if Main.exe is up to date, if not, kills it and pulls/down and launches the new one.
I guess this is still two exe's but only requires install of one.
Any thoughts on most elegant way of handling this?
S