Problems with update script

[greyhound]

Am current evaluating IA with a view to it replacing IS11 with particular emphasis on it handing application updates.

Not sure if this is my lack of understanding or not but there seems to be a number of issues with the default update script that is added to a project.

1. The UPDATE_DOWNLOAD and UPDATE_AUTO variables seem to be initially undefined when running the update, have had to define these myself to get it going.

2. The details of what has been applied in an update is written out to the installedupdates.dat file in the $EXEDIR$ folder. This appears to be a temporary folder and is different each time the setup is run in update mode, thus the details of previously installed updates is not available when next run.

Would appreciate comments.

Generally product looks good albeit somewhat quirky, found it difficult in some places to understand the help. Could really do with more examples.

Regards
Graeme

[MichaelNesmith]

1. These variables are defined by the update scheduling process, which is part of the update script. If you haphazardly deleted the part of the script that runs the update scheduler, you may have broken the logic. Note that if you don't want a scheduler, this forum does contain a pre-built update script capable of running directly.

2. Did you actually test this behavior at runtime? Because then you would have seen that this $EXEDIR$ is where the installer is cached locally on your machine after a successful install. Or, again this might be caused by your script modifications, if you did test at runtime and the test failed.

[greyhound]

re: 1 - can you let me know where on the forum I can find that update script?

Rgds