Currently, it would appear that if we send a customer a modified file for them to override one of our standard files with that the next time they attempt to do an update via wyUpdate, the update will fail:
An error occurredThe update failed to install.Patch failed to apply to ....Exception of type 'System.Exception' was thrown.Click Finish to exit
I've already reported that pressing "Finish" does not appear to roll back the failed installed.
However, for our customers - at the very least during beta cycle, and to a lesser extent during release cycles - this is going to be a fairly common occurrence. Our software is basically a runtime engine for a custom scripting language. Those scripts occasionally have errors in them that can be easily patched by simply sending the suffering customer an updated single script file to replace the standard script file with (there are over 4,000 scripts, each is relatively small - fifty lines to maybe a few hundred).
So:
1. Improve Error Message: I would like to see the error expressed in a way that makes it crystal clear that the problem is that the file in question is not what was expected, rather than 'system.exception', if this is easy to do.
2. Offer to skip the file in question. It is possible that the file is the latest version of the script, so the patch being applied would only end up with what is there anyway.
3. Fix the rollback bug. The user should be able to roll back on a failed patch.
4. Other ideas? I'm not sure what other thoughts you guys have in terms of this? Maybe there is something we can think about doing to improve the work flow from our end...?
