Dear members of the Appeon community,
we are currently migrating our sources from PowerBuilder 10.5 to the new PowerBuilder 2017/R2. Unfortunately we have some problems with the new Subversion integration.
In general the migration works without problems. For the first test I opened the workspace for the first time, got the popup that asked for migration. After confirmation the migration process started and after a full rebuild of the project, our program was runnable without further adjustments.
I am now preparing our developer machines. This time I do not simply copy the sources manually onto the machines for migration, now I want to attach our Subversion source control (version 1.9.7) to the PowerBuilder IDE to get the source files.
Thanks to the native Subversion integration in PB 2017/R2 we do not need additional tools to establish a bridge between Subversion and PowerBuilder. I just selected "Connect to Workspace" and entered the subversion repository URL and the local checkout directory:
Then the download of the sources started without problems, but after the download I got the message that Powerbuilder was not able to open the targets that are included in the workspace and removed them from the project.
As a result the workspace was empty as the targets we missing. I was curious about the reason why the targets could not be opened. So I tried to add the existing targets manually into the workspace to get more information about the cause.
The error message said "bad application library" that were referenced in the target file.
My assumption is that Powerbuilder does not like the library files from the subversion repository because they are not migrated yet. Of course I could take my local files from the first migration and add them to the repository, but in that case I would create an entire new repository item from scratch in Subversion instead of continuing the current one. So I would loose the entire check-in history.
Is there a way I could retrieve the workspace from the source control, execute the 2017/R2 migration and do a check-in back into the repository?
I'd appreciate if you share your ideas.
Many thanks in advance and best regards