Being new to automatic web update process, certain
aspects are unclear after reviewing the documentation.
SITUTATION
1. My original install conatins about 50 files
2. A given update that I provide will contain just a few
of those files that get replaced on the user's machine.
QUESTIONS
3. Where do I define which files go into an update pack?
Do I create a whole new project with just those files
to update in it or can it be defined within the setup
of the master project?
4. In the monitor URL field on the project properties field,
do I put the full path to the UPDATE.INI file or to
the update patch file itself (myFile.exe)
Thanks,
Dan
Web Updates Issue
OK about 50 files in an install, so perhaps those are split between different features ? Those features along with perhaps other items your install may require (eg. Microsoft Installer) will define your web media blocks. The fact that you only want to replace a few of those files will be sorted out by IA depending on what changes it determines have been made since the previous release. So,
1. Change your version number in project properties.
2. Create a patch reference or references which link to your previous release (or very importantly, releases) respectively.
3. Ideally but not necessarily, name your update pack to the new version number in 1.
4. The reference in the box below this is the FULL path to the installer for the update ie. the patch. Whereas the project properties path you mentioned is the path to the updates.ini file which the client installer can determine whether an update is available from or not.
5. Make your new version web build.
6. Build a patch (you decide if its for whole files or binary patching, in project options) and place it on your server at the end of the path indicated in the first part of 4.
Bottom line is you don't decide what goes in to the update, IA does this all for you. It is actually not particularly difficult and once you get to grips with the overall view of web updates and patching, it is a fabulous system, but you MUST also have full copies of your previous web release(s) for patch referencing.
HTH
Pete B.
1. Change your version number in project properties.
2. Create a patch reference or references which link to your previous release (or very importantly, releases) respectively.
3. Ideally but not necessarily, name your update pack to the new version number in 1.
4. The reference in the box below this is the FULL path to the installer for the update ie. the patch. Whereas the project properties path you mentioned is the path to the updates.ini file which the client installer can determine whether an update is available from or not.
5. Make your new version web build.
6. Build a patch (you decide if its for whole files or binary patching, in project options) and place it on your server at the end of the path indicated in the first part of 4.
Bottom line is you don't decide what goes in to the update, IA does this all for you. It is actually not particularly difficult and once you get to grips with the overall view of web updates and patching, it is a fabulous system, but you MUST also have full copies of your previous web release(s) for patch referencing.
HTH
Pete B.