Quote by Merlin
You are absolutely right Frank, but that no longer works on some (many) machines. I have not changed the way I do anything, but will have to in the future.
As far as I can determine, msi by default creates a log of what has been installed and when there is a new install it removes any files and directories that are not in the new install. There is a flag to tell it not to create this log but it seems that on the latest versions of msi this flag is ignored. I cannot find a way around this. The only possibility is, pain though it is, to put every file in every install. I am testing that theory today.
Hallo Merlin,
schau mal bei Deinem Installer nach Optionen wie "Compare Timestamp" oder "copy if not installed". Beim ISTool kann ich diese Optionen bei jeder Datei angeben, evtl. gab es da bei Deinem Installer eine Änderung.
Aber abgesehen daon, würde ich einfach jede Installation als VollInstallation durchführen lassen. So gibt es dann immer nur ein Setup und fertig. So arbeite ich mit meinen Setups seit vielen Jahren.
Bei einem Tool nutze ich das "TMS Webupdate" hier werden aber eigene Patchdateien von diesen Tool erzeugt und es werden nur die Änderungen von der Webupdate-Komponente geladen und installiert.
Thorsten
-----------
Hello Merlin,
have a look at your installer for options like "Compare Timestamp" or "copy if not installed". With the ISTool I can specify these options for each file, maybe there was a change in your installer.
But apart from that, I would simply let each installation run as a full installation. So there is always only one setup and done. This is how I work with my setups for many years.
With a tool I use the "TMS Webupdate" here however own patch files of these tool are generated and it only the changes of the Webupdate component are loaded and installed.
Thorsten
Attachments
Filename: | 13-07-2023_10-26-28.png |
Filesize: | 110.5 KB |
Title: | |
Download counter: | 101 |