Hi Marcelo,
Notwithstanding Armeen's reply, so maybe his engineer will offer some additional insight/ approaches, but here are my thoughts:
I believe I understand what you're trying to do and so I'm thinking you should be able to accomplish what you want by placing a windows command, in this case regedit /s MyRegFile.reg, in the Preload Event in the Run Options tab of the PowerClient project. Create your registry file in advance (and include it in the External Files tab) in one of two ways depending on whether you want this app to be user specific or machine specific:
IE...
Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\PB190.exe
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\PB190.exe
You probably know how the Default & Path entries for this registry subkey should be structured since you included an example in your reply to Armeen so I won't go into that. If the Path folders you're referencing also have to be created in addition to the registry settings then you could use the Preload Event for that as well.
Of course the above assumes that permissions or other GPO settings won't prevent changes to the registry on the client machines.
Again, Armeen may come back with another way to do it (or the way it's supposed to work) and even if the above doesn't work for you I wonder if the ability to make registry entries might be a nice enhancement for the PowerClient Project.
HTH...regards,
Mark
Glad to hear that you solved the issue! And specifying full path in the Windows app registry is currently the most convenient way to add folders to an executable.
Regards,
ZhaoKai
From now on they can only keep improving powerclient.
Things that I am interested in that can be done:
1) Customization of powerclient startup and update interfaces.
2) Add macro variables and documentation for the preload commands of our application.