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
Sorry for jumping in here, but have you looked into the use of deployment version, min version, available/expire times?
powerclient: https://docs.appeon.com/pb2022/pbug/creating_a_powerclient_project.html#defining_an_ica_project
powerserver: https://docs.appeon.com/ps2022/Manage_app_versions_and_updates.html
For powerserver, there is the additional issue of the webapi version having to be compatible with the deployed/running version of the downloaded PB parts. I do believe this is manageable, but for this thread (powerclient) it is off topic.