- Gene Kanten
- PowerBuilder
- Thursday, 4 February 2021 01:41 PM UTC
We are currently migrating from PowerBuilder 2017 R3 to 2019 R3.
We are using Git for source code control.
In our application Git repo we have multiple folders at the root level, one of which is our Powerbuilder folder, which contains all the PowerBuilder files. The other folders have to do with other files needed for installation, database stuff etc.
Can someone please confirm that the PowerBuilder workspace file has to exist at the root level of our repo (i.e. where the .git folder exists)?
And also confirm that the ws_objects folder gets created in the same folder as the workspace file.
Currently our workspace file exists in our PowerBuilder folder but when we open that workspace we don't have access to any of the new Git functionality (like creating and switching branches). I'm assuming because it can't find the .git folder and so has no idea that it is using Git. Is that correct?
I would prefer to keep our workspace file in the PowerBuilder folder but I assume to do that I would have to create a Git repo for that folder in order for PowerBuilder to know it was using Git and then I would have a nested Git repo.
What is best practices? Should I have one repo or a nested PowerBuilder repo?
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.