- Andreas Müller
- Beta Testing
- Tuesday, 17 December 2024 01:55 PM UTC
Hello!
Since the new solution format requires a switch to either git or svn, and git being the industry standard, we decided to choose that as our new version control. A few questions/issues came up while trying to migrate.
1. .pbproj file: Every time an object (e.g function) is created, the source to it is linked in the pbproj file. This will create an conflict, every time objects are added in the same PBL. Is this intended/can this be avoided?
2. Solution changed: When I pull from the server, and there has been changes to e.g. the pbproj file, the IDE prompts me to reload the solution and after that do a build. Will I have to do that everytime?
3. Git commit:
- When I try to do a commit on either the workspace or project, it takes a lot of time to find the changed files. (Up to 30s loading spinner)
- When I commit an object via Powerbuilder IDE, it takes up to 15s and freezes the application for that time. When I do it via TortoiseGit in the file explorer, it's basically instant.
4. No easy way to commit/push: You always have to go to the library painter to commit, scroll to the solution file to push/pull... When you add a object you need to commit the object and the pbproj...
Also it seems like with all the solution reloading and building, the IDE crashes quite a lot.
~77 Pbls, 7000 Objects
These problems/restrictions might slow us down a lot, could it be that svn is a better fit for powerbuilder?
Any advice is appreciated :)
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.