So,
I have an installation package that is rather large. As time has progressed I have made some updates to the "engine" aspect of the application, but the primary "data" the engine works with has remained the same. I have written other scripts in Advanced Installer which find an "installed" file, preserve it, run the 'remove/reinstall' process, and then restores the preserved copy of the file. Very helpful in say database files for a .Net application, which the data has been altered during use, but the executable has be updated and thus we don't want to "delete" the database file, while we still wish to perform an update on the executable.
That is simple enough for a installation package that contains "all" the files. However, I am dealing now with a process of wanting to create a "small" update package. There are say, 10 files in my original installation, and currently I only wish to update 1 of those files. the other 9 constitutes some 70 odd megabytes of data which have not been changed from version 1 to version 1.1. Thus I would like to have the Update installation package be the mere 300 kb of the 1 file that needs to be replaced, while retaining the other ten that exist already installed by version 1.0.
How might I do this? Currently, By creating a new package, it would install a whole new installation, as well, re-using the 1.0 package would incorporate all 73 mb of data. I only want to update 1 file and leave the other 9 alone as part of the same installation.
Is this possible? Other Suggestions on how to achieve this?
Thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
FOLLOW US
Get the latest news in Application Packaging