1. Aleš Vojáček
  2. PowerBuilder
  3. Wednesday, 7 July 2021 12:50 PM UTC

Hi all,

I did use PFC libs in past, but never need to migrate to new version of them.

How do you use PFCs now when GIT is usable in PB2019.

Do you have your own fork of PFCs from https://github.com/OpenSourcePFCLibraries/2019

and then use that fork in your PB projects or do you have pfcs+pfes commited inside every PB project?

 

I have to update pfc which are in applications wich we are migrating to pb2019 and it means a lot of work (after I will replace old pfc/pfe with new one then I need to do changes which were in old pfe libs.

Are there some "best practices" which will help with further migrate to new pfcs? Or it is intended to manualy apply changes in pfes after migrations? Or is it ok to have older pfe lib with new pfcs?

Sorry for question which may be obvious for someone who was using pfcs in past, but I never did when I was in PB6.5 world (we had our own framework in those days). I red about how to use PFC/PFEs, but in that resource was not real life scenarios nor scenarios with git support.

 

Thank you all 

Ales

Bruce Armstrong Accepted Answer Pending Moderation
  1. Wednesday, 7 July 2021 18:50 PM UTC
  2. PowerBuilder
  3. # 1

I'd suggest you maintain your own separate PFC project in source control.  That will ensure that stuff that your company considers its IP doesn't get mingled with the open source project.   Create a fork or the open source project and add stuff to that you want to contribute to open source, but don't mix the two.

As for applications that depend on PFC, the answer "it depends".  If you're going to be doing automated builds from source control you're going to need the PFC layer as part of the apps source control project or you'll want to compile that to PBDs and then reference that from the target application.  If you're not doing builds from source, then you could just reference the common PFC layer from each application and just not put it into source control within that applications project.

Also, the question is: how often is your own PFC/PFE layer changing?  If you're making routine changes to it, then it makes more sense to have it as it's own project.  If it's quite stable though, you could just include separately in each of the applications.  You'd have to update it in each one later if you did modify it, but it you're not making a lot of changes that's manageable.

 

Comment
  1. Aleš Vojáček
  2. Thursday, 8 July 2021 08:05 AM UTC
We does not use automated build, but I'm considering that as new step. For our .NET applications we are using TeamCity + Nuke.

Thank you for your answer. I will try to play with that. I did not use PB since 6.5 so I have to explore to get into best practices for maintain PB projects.

Ales
  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.