Should I just put InstallNow() in UpdateAvailable?
Yep. This will start the update then restart your app.
Do I need to keep all update files (namely *.wyu files) on my server
Yes.
Hello,
I'm currently testing wyBuild and would like to use it for updating our in-house .net applications.There are two things I don't really understand at the moment, maybe someone shed some light...
As we release updates over night, I need to make sure all applications get updated atleast once per day. Therefore I set DaysBetweenChecks to 1 - this should be enough. The problem is that the "old" version gets started and only after another restart of the application the update is installed.Here's what I'm trying to do:- User starts App for first time this day- App recognizes update and immediately updates itself- New version is started
So, I've found ForceCheckForUpdates(), InstallNow() and UpdateAvailable but I'm not sure how to accomplish the above task without needing to start the App twice. Should I just put InstallNow() in UpdateAvailable? But this will not prevent my App from being loaded. Not sure what's the "best practice" here. 🙄
BTW: Do I need to keep all update files (namely *.wyu files) on my server or can I just keep the latest all.to.x.y.wyu file?
Thank you very much in advance,Keeper
Should I just put InstallNow() in UpdateAvailable?
Yep. This will start the update then restart your app.
Do I need to keep all update files (namely *.wyu files) on my server
Yes.
Hi Sam,
thanks for the quick reply!So, to clarify this - the best way would be to show some kind of splash-screen while checking for updates (wait there until the automatic updater control finished) and then call InstallNow(). Right?
Regarding the update files. I disabled Patch compression and therefore have files like:test.all.to.1.1.wyutest.all.to.1.2.wyutest.all.to.1.3.wyu...
In this case, do I really need to store every file? In my understanding I only need test.all.to.<latest>.wyu?!
Thanks again,Best Regards,Keeper
So, to clarify this - the best way would be to show some kind of splash-screen while checking for updates (wait there until the automatic updater control finished) and then call InstallNow(). Right?
That's not really the best behavior. You should include the automaticupdater on your main form. Then if you're doing one of your forced updates, and there's no update already pending, then use wyUpdate in standalone mode.
The difference between wyUpdate and the automaticupdater is that wyUpdate works best in synchronous scenarios, while the automaticupdater is asynchronous thus working best in the background.
Does that make sense?
Hi Sam,
yep, that makes sense. Thanks - will look into using wyUpdate in standalone mode.
Best Regards!