I have made an msi-setup file using installaware which installs components to the client pc (such as dll and ocx files).
The msi-file is located on a default location on the server.
My tool has to check if this msi-file is newer than the setup which already has been installed on that machine.
Using windows explorer-->properties I can only see the revisoncode, createdate and changedate, but no version number is present.
Is it possible to add a versionnumber to the msi properties ?
I don't think just checking if the revisioncode's are different is "bullet proof".
If, fore some reason, an older version of the msi will be placed at the server, the revisioncodes will be different and my program will start the old msi file, which, obviously, is not desirable
p.s.
I'm using Visual Basic 6.0
Auto detect update
Auto detect update
Ton Blokhuizen
Tooling Engineer
BMA BV - Netherlands
[i]BMA: leading the way in obstetrical data management
http://www.bma-mosos.nl[/i]
Tooling Engineer
BMA BV - Netherlands
[i]BMA: leading the way in obstetrical data management
http://www.bma-mosos.nl[/i]
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
You can try another mechanism to check for versions in your script - have setup write its version to the registry or a system folder, and have the "new" setup read from there.
Also see the new Web Updates feature.
Also see the new Web Updates feature.
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
The only "problem" is, is that the "new" setup must be pushed by my tool.
For the "meganism" you suggets, the setup (if is is new or not) must be run every time my tool is started....
The problem is is that the folder at the server ALWAY'S have an msi file present.
My tool checks if a setup has been deployed or not, and if not it will start it.
When you start the tool the second time, it detects that the components are installed.
From now on every time the tool startst, it has to check if there is an update available, using the same msi-file in the default folder.
For the "meganism" you suggets, the setup (if is is new or not) must be run every time my tool is started....
The problem is is that the folder at the server ALWAY'S have an msi file present.
My tool checks if a setup has been deployed or not, and if not it will start it.
When you start the tool the second time, it detects that the components are installed.
From now on every time the tool startst, it has to check if there is an update available, using the same msi-file in the default folder.
Ton Blokhuizen
Tooling Engineer
BMA BV - Netherlands
[i]BMA: leading the way in obstetrical data management
http://www.bma-mosos.nl[/i]
Tooling Engineer
BMA BV - Netherlands
[i]BMA: leading the way in obstetrical data management
http://www.bma-mosos.nl[/i]
The way I have accomplished this task is to have my original setup write a registry value with the installed version, then my tool checks the registry version against an ini file on the server that contains a version entry, if the version in the server ini file is greater the new setup is started.
Jim Oswell
Software Engineering Manager, Dental
Greenway Health, LLC
http://greenwaymedical.com
Software Engineering Manager, Dental
Greenway Health, LLC
http://greenwaymedical.com
Who is online
Users browsing this forum: No registered users and 154 guests