Hi,
I downloaded the new PB2019 R3 beta and have been trying out the new C/S deployment:
1 - How do I configure a remote Server"? I think I have to add FTP protocol/role, but some instructions for noobs would be nice. (or even better, powerbuilder setting IIS up so it would work on remote).
2 - Using "localhost" we have to disable any antivirus to deploy. Avast and Avira consider the code as BAD. No problem for deployment, but this IS a big problem for any clients connecting. Antivirus also jumps in and the only way to download on a client is by also deactivating the antivirus.
3 - How can I embed a Manifest?
4 - I cannot run my applications anymore when the server is down. This should be possible in my opinion, once you have done the initial download. It would give us the possibility to have the file server running while our customers are testing and we are still uploading new requirements or bugfixes, but once we've reached a stable situation, there'd be no more need to have the fileserver running.
5 - Some examples for registering OCX and DLLs would be nice. An example shows the use of regasm.exe, but not all clients have an available regasm. Can we somehow deploy a regasm.exe in the files section and then run it with the script?
Edit: 6 - We are using commandline parameters. How should I fit in a commandline parameter, now that there's already some in the shortcuts produced by the C/S deployment?
regards,
MiguelL
About 1):
Yes I looked at it, still doesn`t work. It does work for a PowerSERVER profile on the same machine, just not for the Powerclient.
About 2):
Yes as a workaround it`s okay, but you can`t oblige your customers to add exceptions to their antivirus, so hopefully Avast, Avira, etc. will update their software to allow Appeon.
About 5):
As Chris said, maybe customers won`t allow you at all to distribute a regasm.exe and I agree. Maybe the way to go is generate the needed registry entries and run them from the command line using regedit.ext (at least regedit is available on customer`s computers). We already know which registry entries we need, since so far we`re using Wix to create our msi installers. Another thing we could do is to add the msi installers and run them from the commandline.
So maybe this one is not so urgent.
About 6):
That would mean that (for now) we always have to run the application from the browser if I`m not mistaken.
Good enough as a workaround for now.
Thank you!
Thanks a lot for your comments!
Regarding #6, after you run the application from the browser for the first time, you can always run the application from its desktop shortcut. The command line argument specified in the application URL will be remembered in the desktop shortcut. It is possible to change the argument value by manually modifying the settings of the desktop shortcut, or you re-run the application from the browser.
Best regards, Julie