Hi Milton;
My Apps are all in sub-folders from the main App so I only get one URL.
It won't matter if you issue a Run() command because of the locating the PB runtime issue in mentioned before. It doesn't matter whether your apps are in the same folder or not.
Another challenge is that the PowerClient Launcher can install the App(s) in different locations depending on whether you choose App install by User or All Users. So there's another challenge.
A way around your multiple URL app deployment might be to not use the Run() approach but maybe the iNet's HyperLinkToURL() method to invoke the secondary URL(s). However, another current limitation to the PowerClient Launcher is passing parameters (arguments) from AppA to AppB for example. It currently doesn't support that. Then even if Engineering addresses this limitation. How does AppB return a completion code back to AppA - which Run & Wait code like Roland has for use or my STD framework uses to allow return codes (which the Run command does not support).
So there are certainly some more design challenges to overcome. However for now, Appeon Engineering is focusing on the "basic" deployment & remote PC launcher testing. I'm sure that other betas will address more functional requirements. Please open beta support tickets though for any shortcomings or issues that you find so that Appeon can formerly track these.
BTW: A great question!
Regards .... Chris
I have reported to Julie and product@appeon.com
and they are actually very serious and responsive. So I think they are considering all suggestions given.
SOOOO good Appeon has taken over from the SAP and Sybase disasters :-)
With Appeon, we developers have a partner, not simply a vendor.