The PBG file could be eliminated without eliminating the PBL file.

All they would have to do is change the PowerBuilder IDE to require that all PBL files be located in a separate folder named after the PBL file. This is what was done for PB.Net, the object files were located in a folder named libname.pbl.

The SCC API has a function which you can call to get a list of all the files in a folder. The PowerBuilder IDE cannot use this because developers are allowed to have the PBL files located in the same folder. That is why the PBG file exists.

From what I heard at the Elevate keynote presentation, Appeon has reversed the decision to eliminate PBL files - they will be around for the foreseeable future. As Chris mentioned, PB 2017 R2 will natively support GitHub and SVN.

I personally use Plastic SCM. It has a unique graphical interface and an intuitive approach to branching and merging. Plastic provides an SCC-compatible plug-in, which is needed to work with PowerBuilder, but causes issues from time to time, usually related to the PBG files (another reason to get rid of the PBL). I'd recommend at least checking it out: plasticscm.com

Hi Gimmy;

   FYI: In the next release of PowerBuilder (PB 2017 R2) coming in December 31, 2017 - the PB IDE will be able to communicate natively with either the GitHub and SVN SCM's. I personally use SVN but I know many here on this forum use GitHub as well. Both SCM's today require a "proxy" 3rd party plug-in to work with the PB IDE. For this reason, PB often has issues with dealing with the SCM at "arm's length". The native implementation will be a lot easier to install, configure and interact with IDE wise.

  So if you are not in a hurry, the PB 2017 R2 release coupled with an open source SCM described above might be for you.

Food for thought.

Regards ... Chris

http://www.topwizprogramming.com/wizsource.html

Microsoft Team Foundation Server