I have implemented an updater for one of our products which works no problem. The updater.ini file points to a updates.txt file on the URL specified. When I do an update configuration I can either point the updated product to using either a URL, a network path or a local path. Again all these work. However we have customers who are overseas and download time for 20pcs may take some time. They would benefit downloading to a network path. Other customers will have no problem downloading from our website.
My initial solution to this problem would be that each customer has a different updater.ini file and using the copy/move file operation in the files and folders section I could then configure the updater.ini on the customers site to point to their own specific customer_updates.txts prior to installing the product. So when the product is installed it copies their unique updater.ini file into their apps folder.
As I could not delete the actual updater.ini file from the files and folders section will the copy actually work because I'm not sure if 1. the ini file in the msi is installed b4 the copy takes place and 2. does it overwrite the installed version.
If this works I could then create different update configuration txt file for each customer where we could then decide where they will be downloading the updates from.
I hope that makes sense
Thanks
FOLLOW US
Get the latest news in Application Packaging