Printable View
I use the webinstaller for one of my products. I send the customer a
link to the webinstaller setup.exe.
The problem is that customers will download the setup.exe but not run it
for weeks.
Meanwhile we post a new release. They run the Setup.exe they have and
get the mismatched - not expected error message.
Is there any way to have the Setup.exe check to see if there is a newer
version of itself?
Paul MacFarlane
Hi Paul,
In your scenario, I would suggest to check (from your Web Installer) the
currently installed version or build.
Let us assume your customer is on Version 1.6. You sent links to 1.7 and
later 1.8 but they "forgot" to install it. Now you send out Version 1.9.
Let the Web Installer check the required previous version (e.g. Version 1.8)
and you are done. If the customer is not on a valid previous version,
display an error message and ask him to apply the previous version(s).
Or develop the setup.exe in such a way that it can automatically handle it.
For example, our own SetupBuilder 10 installer and web update can bring any
previous SetupBuilder 10 to the latest build.
Friedrich
Friedrich,
We are not patching. Every release is a full release. The link is always
the same (doesn't change with each release)
Example 1: Software Never Installed.
They downloaded the Setup for v1, we're on v3. The run Setupv1 and get
the error.
Example 2: Software Installed v1.
They installed v1 fine. We release v2. They re-run Setupv1 because
they had saved it before.
Is there a way for the Setup stub to download the 'version file' and
compare it's version to itself?
It knows where it is because it'll be downloading are the files from
there (wucheck does at least -but I can't use that on first install.)
Then, compare the versions and if out of date display a message saying
'a newer setup is available' and run it - like wupdate.
Thanks,
Paul
Paul,
aha, okay. I understand. I'll give it some thoughts and get back to you.
Friedrich
Thanks !
Paul MacFarlane
Hi Paul,
I have uploaded a demo project for you.
http://www.lindersoft.com/projects/W...ersionTest.zip
You can use the following method:
1. Use the "#create folder..." preprocessor to create the \Web subfolder
during the compilation process.
2. Use the "#edit ini..." to create a versioncheck.ini file which holds the
version number.
Always upload this versioncheck.ini to your server when you make a new
installer available.
3. Let the installer download this very small versioncheck.ini (30 bytes)
and do a version comparison. If the version on the server does not match
the "stub" version then display an error message and abort the installation.
This is security software friendly.
Of course, you can also let the stub check the version from your setup.exe
file located on your server, but then you have to download the larger
setup.exe (instead of the versioncheck.ini).
Does this help?
Friedrich
BTW, I'll make this functionality available soon as a pre-build include
script (.sbi).
Friedrich
Looks great.
Q: Why did you create another versions file instead if using the "server
manifest file" created by the web update settings?
Paul MacFarlane
Hi Paul,
> Q: Why did you create another versions file instead if using the "server
> manifest file" created by the web update settings?
If your application supports web update and both the web update and full
install always have the same version number, then you can use the server
manifest file, no problem. My provided method also works for beta and
internal test versions, etc.
Friedrich