In the current build, if you add the MD5 signature to the updates.ini file, it causes the ;aiu; error.
Unchecking this option on the project allows the update to run without error.
Any reason for this (server is running IIS 6 and has .ini as a MIME type).
We cannot reproduce this on our computers. Make sure that the file pointed by the "Downloads URL" field in the project is the same with the one you browsed when you add the update.
Having trouble reproducing it myself now, but struggled for a couple of hours yesterday with this problem after triple-checking the paths etc. in the file.
Maybe a suggestion, considering the ;aiu; error is reported to end-users, could you not make it more user friendly and report an error code that is more meaningful as to what is actually wrong with the update check?
e.g "Sorry, unable to check server: code -417". From trying to get this to work yesterday, reporting ;aiu; missing when it is clearly in the file on the first line is somewhat meaningless.
Lastly, I really like the update feature, but it would be nice if the updater.ini file containing all the connection info was not user-accessible. Have you thought about burying this in the registry, or compiling it into the updater as a resource?
FOLLOW US
Get the latest news in Application Packaging