Hi,
Can an app deployed using Power Client periodically check for updates then if there are updates then download them, apply them and restart it self ?
any clue ? :-)
Thanks
// Steen
Hi,
Can an app deployed using Power Client periodically check for updates then if there are updates then download them, apply them and restart it self ?
any clue ? :-)
Thanks
// Steen
Hi
What Steen requests would be great. I'm looking for similar option. It would be fine if CloudAppLauncerService periodically checks the new version availability and download it to some cache as a background task. For users connected through i.e. WiFi this would be a significant improvement because currently they have to wait until the application is downloaded.
In powerbuilder there's this "Restart()" command (can't access PB now, so not completely sure about naming and syntax).
Also, you could have a look at Roland Smith's PBUpdater, maybe it could serve you somehow: https://www.topwizprogramming.com/tools.html
regards.
Hi Armeen,
I understand your point completely.
We would so much like to use the awesome PowerClient. But we have an architecture where we use the Run() command to run different PowerBuilder exe files. Will that work when the "main" exe has been launched using the the Cloud App Launcher ?
Also, once the Clod App launcher have started the main application and all is updated etc. can the exe subsequently be started just by running the exe?
Thanks
Steen :-)
ps. Please excuse my ignorance regarding the PowerClient. I have very little knowledge about it but I think the concept is brilliant and I very much would like to use it.
Hi Steen;
No it cannot currently. However, that is what I have been suggesting as an enhancement request in this thread ...
Regards ... Chris
Whenever the user starts the application, the Cloud App Launcher manages the updating process in manner that is seamless to the user and the user does not have option to opt out of updates. In other words, you as the developer dictate when updates go out.
Our recommended approach is to perform updates during scheduled maintenance periods. You don't want older instance of the app to be in use while database is being updated. So the scenario you described of hot updates while app is in use is not something we plan to enhance in our roadmap.