QUESTION TO ENGINEERING...
When the CAL needs to be upgraded to the next runtime build of PowerBuilder,
does it look to see where it's installed on the Client workstation by
1) using the Registry to determine the Users' AppData location, OR HOPEFULLY,
2) does it use the location of the current installation of CAL on the Client?
I've successfully been able to have the CAL be installed in a non-User-AppData locale
on the client and have all its Registry key values reflect this by
running the CAL's MSI OR a customized CAL's install EXE while temporarily changing
one of the Registry key values for User Shell Folders to the desired value.
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
Local AppData = %USERPROFILE%\AppData\Local
...to...
Local AppData = C:\<DesignatedFolderName>
In our Use Case, we need to configure a core/"gold"/default
Virtual Desktop that is distributed to all Users.
Using %USERPROFILE%\AppData\ is not acceptable for this requirement.
Using a customized CAL...
...in concert with this install-time User Shell registry modification,
we can have both PowerClient-deployed application and the CAL
installed to all Users' logical C: drives.
*** But what happens on the client workstation when we create and deploy to IIS,
*** the customized CAL that implements the NEXT PowerBuilder runtime version?
*** Does it look to see where it's installed on the Client workstation by using the
*** Registry to determine the Users' AppData location, OR HOPEFULLY,
*** does it use the location of the current installation of CAL on the Client?
Armeen indicates that this will be supported natively by PowerBuilder 2022 (excellent),
but what of post-1506 builds/runtimes of PowerBuilder 2021?
Thank you.
Please clarify/confirm...
>> 3) If you customize the 2022 CAL, you can define the installation directory.
The installation directory of CAL on the client?
...or do you refer to the installation directory of PowerBuilder applications?
Thank you both.