Hi Armeen,
I do not understand completely.
Why does Appeon not recommend this approach of downloading all at start up. Does it not work well ?
Also, is it possible to somehow have multiple versions deployed and then have a single "boot" application that directs to the url holding the latest version at start up. or something like that :-) .. again excuse my lack of deep insight into this topic.
I would really like an in depth description of the exact workings and deployment scenarios with pro/con descriptions.
(I have read the current one that talks about the individual objects etc.. may extend that article)
It is way to much time to invest into PowerClient or PowerServer just for trying it out and finding out how it works.
To me the important thing is : What happens when the app is upgraded and what are the recommended strategies by Appeon for doing the upgrades that in our case happens once a week.
The "just do it when no-one is using the app" is NOT in any way a viable solution as people are using the app across the world in different time zones and some are not closing it for weeks or moths. So I really would like a good and recommended strategy. Otherwise I would just have to leave the PowerClient and for that matter PowerServer on the doorstep for now.
//Steen
I think the concept is brilliant!
Can you recommend a good strategy for updating an application that is running on multiple machines.
Maybe a forced shutdown (not so nice) or even better a changed URL to the new version so that they continue to run unaffected and then the next time they start the app they will run the new updated version.
The latter I think could be very cool.
//Steen
ps. please excuse my lack of knowledge in this field.
What is the recommended deployment method which you can suggest without crashing the application?Actually, users are used to do double clicking the application shortcut and updates will downloaded to their local machines. They don't want to download the updates through the URL (web browser). What to do?