Hi again, Wyatt.
I'm now exploring your AutomaticUpdater component.
I've made a little WinForms test project using your AutomticUpdater component. Now the problem is that when the update process starts, a dialog pops up requesting the operator to close some (blocking) processes before the update will continue. The problem is that the list of blocking processes is absolutely empty! This dialog persists until the user clicks the "Cancel Update" button whereby the whole process is aborted. What am I doing wrong?
- Martin.
Martin,
This is a usability bug on our part. I'll tell you what's happening: there's an exe running (one of the exe's in the folder you're updating to) however it's a window-less exe. Exe's without a running window don't have "window text" thus the list appears empty. If you click near the top of the list, however you'll be able to select the running process.
We'll have a fixed version out in about a day. It will show the window text along with the exe name.
Thanks for spotting this.
Hi Wyatt.
I too noticed that it was possible to selecet the invisible blank line in the top of the list box, but all attempts to stop the invisible process failed ("Close Process" and "Close all processes" buttons both had no effect).
The only .exes in the folder are my test project (AutoUpdateApplication.exe), wyUpdate.exe and AutoUpdateApplication.vshost.exe. I suggest it is the latter one causing the problem (because i run my application directly off Vistual Studio).
When running the application without having Visual Studio started, the empty "Close Processes..." dialog still displays, but only for a short moment (half a second or so) and the update process completes ok.
In my opinion you should 1) Make wyUpdate immune to .vshost processes (so that applications can be run directly off VS) 2) Prevent the "Close Processes..." dialog from appearing at all if it's empty - even though it's only for a short time (it looks really ugly).
-Martin.
When running the application without having Visual Studio started, the empty "Close Processes..." dialog still displays, but only for a short moment (half a second or so) and the update process completes ok.
This will be fixed in the upcoming version. It will be out either today or tomorrow.
Make wyUpdate immune to .vshost processes (so that applications can be run directly off VS)
We will releasing a debugging version of wyUpdate that allows you to test the AutomaticUpdater control without actually updating files and folders. This will be released around the time I write a blog post announcing v2.5 of wyBuild. About a week or so from now.
wyBuild & wyUpdate 2.5.9 are now out. Both the bugs you mentioned (flashing process box and process titles not showing) have been fixed.
Hi, Wyatt.
Thank you for for the bug fixes - I'll try them out. However, I need an extended period of evaluation time. I have only a few days left but still a lot to check out. Will that be possible?
Currently I'm exploring the AutomaticUpdater control and for now I have a the following question:
When a new version is available: Is it possible to get access to and display the "changes notes" for the new version to the user before he decides to actually download and install the update? Maybe he doesn't want to update if the changes are all irrelevant to him. I can't get the AutomaticUpdater control to work that way.
Ideally I want this:
1) A new version becomes available2) My appliction announces this to the user3) The user clicks a button to get more info about the new version before deciding4) My application displays the "changes notes" for the new update while continuing to function normally.5) The user clicks either "Cancel" (nothing more happens until next version is released) or "Download & Install".
Download & install:
6) My application downloads the updates7) My application closes down to allow files to be patched and replaced8) My application restarts automatically (in the new version).
The important thing here is to give the user the opportunity NOT to update based on what he can read in the "changes notes" - and to allow the application to continue to run without interruption if the user chooses not to update.
Is the above scenario possible with AutomaticUpdater? If not, what would you suggest I do instead (while still using AutomaticUpdater)?
-Martin
Thank you for for the bug fixes - I'll try them out. However, I need an extended period of evaluation time. I have only a few days left but still a lot to check out. Will that be possible?
Yes. Send me an e-mail and I'll send you a trial extension. wyatt@wyday.com
Currently I'm exploring the AutomaticUpdater control and for now I have a the following question:
When a new version is available: Is it possible to get access to and display the "changes notes" for the new version to the user before he decides to actually download and install the update? Maybe he doesn't want to update if the changes are all irrelevant to him. I can't get the AutomaticUpdater control to work that way.
Ideally I want this:
1) A new version becomes available2) My appliction announces this to the user3) The user clicks a button to get more info about the new version before deciding4) My application displays the "changes notes" for the new update while continuing to function normally.5) The user clicks either "Cancel" (nothing more happens until next version is released) or "Download & Install".
Download & install:
6) My application downloads the updates7) My application closes down to allow files to be patched and replaced8) My application restarts automatically (in the new version).
The important thing here is to give the user the opportunity NOT to update based on what he can read in the "changes notes" - and to allow the application to continue to run without interruption if the user chooses not to update.
Is the above scenario possible with AutomaticUpdater? If not, what would you suggest I do instead (while still using AutomaticUpdater)?
-Martin
This is almost exactly what happens if you set the AutomaticUpdater UpdateType property to "OnlyCheck".
[attachment=1]auto-update-just-check.png[/attachment]
Your users will be notified of the new update, and they can decide when to download & install the update:
[attachment=0]autoupdater-onlycheck.png[/attachment]
However, there isn't currently a way for the user to reject updates. Do you have users requesting this functionality?
