I had a strange issue last week in which an auto update completely removed my application/windows service. I Think it was failing due to some registry entries - i have some persistent entries which had default values "Select One". so...
When in install the application i pick some values from a drop down menu, these are the values written to the registry. When the update runs it uses these values to answer the dialog during the update (so we don't need used input) I noticed after my last update, these values had been defaulted to "Select One" and realised I'd got the persistent properties set wrong. I updated these and tested in my dev environment and all went great.
Now, in (my lack of) hindsight i should have tested further, as it seems that any servers that had previously updated and had the new "select one" values were failing to update, even worse the application was being ripped out completely
I can't have this happening - luckily only a few dozen machines were affected. How can i stop this from happening? That is,
i install version 1.0 - works perfect
i package an update 1.1 with an unknown bug
my servers download this version
the installation fails
The original version/files that were installed are kept there, no files are removed
I fix the update and repackage it
at the next check in interval the newer version is download and installs (because the update file has changed on my update server, is that right?)
How can we do this? And please explain gently. I don't have a developer brain!
Also, great product!
FOLLOW US
Get the latest news in Application Packaging