1. Aleš Vojáček
  2. PowerBuilder
  3. Saturday, 26 June 2021 00:00 AM UTC

Hi all,

I have some application which I merged from PB 12 -> PB2019R3 and add it into GIT repo.

That app uses old PFCs/PFEs.

How I have to upgrade PFCs?

Is it ok that I will update PFC pbls and It will generate new ws_objects for changed pbls?

Or I have to remove ws_objects/pfc* dirs, change pbls and then it will generate new exported files?

 

Thank you Ales

Benjamin Gaesslein Accepted Answer Pending Moderation
  1. Tuesday, 29 June 2021 05:35 AM UTC
  2. PowerBuilder
  3. # 1

Hi Ales,

I would recommend not touching the PBLs at all. Just update the ws_objects/pfc... folders and then do a refresh from the Powerbuilder UI. This will update the PBLs from the source code files. You can then push all changes to git.

Comment
  1. Aleš Vojáček
  2. Tuesday, 29 June 2021 06:24 AM UTC
Hi,

thank you. But if you want to update PFC from really old version there will be a lot of changes. Do you recommend delete all old ws_objects (from PFC libs) and replace them with exported files from new PFCs?

Ales

  1. Helpful
  1. Benjamin Gaesslein
  2. Tuesday, 29 June 2021 06:41 AM UTC
Yes, deleting the old files first is the way to go. Otherwise deleted files might be retained in your PBLs.

Are you getting the new PFC from Bruce's github repository? ( https://github.com/OpenSourcePFCLibraries/2019 ) You can also overwrite your old pbls with those from the repo before using the refresh in PB. This way you might save some time because PB won't have to refresh as many source files. It's most important that the ws_objects folder is up-to-date, though.
  1. Helpful
  1. Aleš Vojáček
  2. Tuesday, 29 June 2021 07:21 AM UTC
Do you mean that I will replace all pfc pbls and ws_objects from that repo?

I will try that.

I will pray that I do not have to do much changes in pfe :-)

Thank you.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.