I am having an odd problem with web update patches. My verison is 6.6.
The problem arises when I have multiple update packs per version. For example here is the updates pack section of my updates.ini:
[Update Packs for Versions]
1.0.0.1=1.0.0.2$NEWLINE$1.0.0.3
1.0.0.1=1.0.0.2$NEWLINE$1.0.0.3
1.0.0.2=1.0.0.3
Now, when I start my application and it checks for updates by calling the installer with the /update switch, everything is fine. It downloads my two new versions (assuming I'm on version 1.0.0.1) and installs them without a problem.
The next time I start the application however and the installer gets called again to check for any patches, it once again tells me updates are available (which there are none). When I view the "Choose Updates to Download" dialog, both the "Update Title" and "Details" sections are empty (there is nothing to select). The only option is to press cancel.
This only happens when there is more than one version patch. If I change version 1.0.0.1 to this:
[Update Packs for Versions]
1.0.0.1=1.0.0.3
The empty update dialog stops appearing. Why would multiple patches cause this empty update dialog? Please let me know what I can do to resolve this issue.
Thanks,
Chad
Multiple Patches for a version problem
Does no one else have this problem? Are very many of you using the "web updates" functionality. I can recreate the problem pretty easily.
It only started showing up when I started patching only the previous version and not all previous versions (all preceding builds). Prior to the change I would build a patch looking at all previous versions, version 1.05 patch would contain patch references to installs 1.01 thru 1.04. The patch process would get slower and slower each time I put out a new patch (because it had to compare to all of the previous installs to the most current). This method would allow the user to get one update patch regardless of which version they were on.
For fear of my patch process getting to slow down the road, I changed to only patch against the previous install (ie 1.05 would patch itself against 1.04). I was then assuming the user could download multiple patches if needed, so if they were on 1.01 they would download four different patches to bring them up to 1.05. That's when all of the trouble started, something happens when I update my updates.ini for a version they have already applied a patch. So, if they originally installed 1.02 and patch up to 1.04, then I go into updates.ini and append 1.05 onto the end of version 1.02, it would get all confused and after installing the 1.05 patch I would continue to get the blank download window. It thinks another patch is available, but in fact the software is up to date.
Sorry for rambling, but I just wanted to know if anyone else has run into this problem.
Thanks,
Chad
It only started showing up when I started patching only the previous version and not all previous versions (all preceding builds). Prior to the change I would build a patch looking at all previous versions, version 1.05 patch would contain patch references to installs 1.01 thru 1.04. The patch process would get slower and slower each time I put out a new patch (because it had to compare to all of the previous installs to the most current). This method would allow the user to get one update patch regardless of which version they were on.
For fear of my patch process getting to slow down the road, I changed to only patch against the previous install (ie 1.05 would patch itself against 1.04). I was then assuming the user could download multiple patches if needed, so if they were on 1.01 they would download four different patches to bring them up to 1.05. That's when all of the trouble started, something happens when I update my updates.ini for a version they have already applied a patch. So, if they originally installed 1.02 and patch up to 1.04, then I go into updates.ini and append 1.05 onto the end of version 1.02, it would get all confused and after installing the 1.05 patch I would continue to get the blank download window. It thinks another patch is available, but in fact the software is up to date.
Sorry for rambling, but I just wanted to know if anyone else has run into this problem.
Thanks,
Chad