just to add, I cannot go any service route, my apps are WPF and also per user installations (not per machine, not elevated, not administrator) https://wyday.com/forum/t/1225/update-with-no-gui-launched-whatsoever/
I'm evaluating wyBuild to work with my WPF apps with the update process completely seamless staying invisible at all times. The users may only notice a quick restart of the app.
1) I have been able to hide the update check process, but not the wyUpdate.exe window for actual update.
a) ----------------If I launch wyUpdate from command line with:wyUpdate.exe /quickcheck /justcheck /noerr /skipinfo http://wyday.com/wybuild/help/silent-checking.php
then the whole update process is actually effective and hidden as long as the app is not open.
b) ----------------But my purpose is to use the AutomaticUpdater type from WPF and control the updating process from within the app.I have tried setting wyUpdateCommandline to /quickcheck /justcheck /noerr /skipinfo but that does not hide the actual update window, I'm pretty sure because this commandline property is only for checks http://wyday.com/wybuild/help/automatic-updates/members.php
So, are the command line arguments for the actual update call to wyUpdate from AutomaticUpdater exposed somewhere?
Or is there any other property or method of AutomaticUpdater or AutomaticUpdaterBackend types that would let me hide the actual update window?
And KeepHidden is for the actual control visibility I believe. And I already have UpdateType set to Automatic
2) If there is no way to currently achieve a completely silent update with the published control types as they are then is there any other way? Would I need to go and create a custom wyUpdate.exe? Anything else?
As this invisibility is my main criterion for an updater, I hope you can help me find a way.
Thanks.
just to add, I cannot go any service route, my apps are WPF and also per user installations (not per machine, not elevated, not administrator) https://wyday.com/forum/t/1225/update-with-no-gui-launched-whatsoever/
You can't hide the updater window because the customer won't know the updating is happening and thus become frustrated. See How can I completely hide the updater (wyUpdate)? for a full explanation and some workarounds.
Of course, if you want to hide the updater window (against our advice) then you can always modify the wyUpdate source code to behave however you like. See: How to make a custom version of wyUpdate.
Wyatt, thanks for the link regarding the wyUpdate source code approach. although i do not know this from practice, i posit that it may be possible to employ a completely hidden updater that does not become frustrating, and which may in fact become highly pleasing for the user. like all things, they can be done poorly, and i would agree that it is easy to get this wrong though.