Hi there
We have a system which which will be deployed at various clients. We want to implement Automatic Updates. The updates will be downloaded from a local server and not from the Internet. The system is huge and we want to prevent the usage of unnecessary bandwidth. Obviously the details for each server will be different (paths, IP addresses etc.) We would want to create one installation package to be used for any customer, BUT:
1. For the initial implementation, automatic updates will not relevant and therefore the updates.txt file will also not be created. We would want to create the updater.exe and updater.ini file initially so that the installation package is "Automatic Update Friendly" for the future.
2. The problem is that the INI should reference an updater.txt file and the INI file does not know where this file will be (We want to prevent multiple installs of the same system for various clients). Each server at each client is different.
3. What is the best way of overcoming this problem?
4. Can an installation file (msi) read or copy an external file which is separately kept with the installation file? If possible we could have independent INI files which will be installed, but not form part of the msi package
Looking forward to hear from you
Systellence
FOLLOW US
Get the latest news in Application Packaging