1. Andres Slachevsky
  2. PowerBuilder
  3. Friday, 2 August 2019 18:37 PM UTC

Hello All

We are finishing the migration from PB11.5 to PB2017 R3.

We need now to move from PBSC to SVN

all the Tutorials and documentation shows how to do it with the first developer using Add to workspace and all the following with connect to Workspace

but it will bring all the workspace from scratch to the developer machine.

Any advice on the best way to set the connecting to SVN to the rest of the developer that already have the PB code in their machines.

will add to source control and then un mark all the objecs will do the trick?


Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 6 August 2019 01:11 AM UTC
  2. PowerBuilder
  3. # 1

PB native support for Git/SVN requires a special folder structure, like the ws_objects folder. You can use “Add to source control” to let PB create the repository and upload it to a bare repository on a Git/SVN server. Other developers can then use “Connect to Workspace” to set up the clone to their local machines.

If you have already cloned the repository using another tool or you moved the workspace folder, PB will not automatically recognize the connection. You can use the following workaround in this situation:

Let us say you have an existing repository in C:\MyWorkspace

1.       Temporarily rename you existing repository in another name C:\MyWorkspace_temp

2.       Create a new folder with the name C:\MyWorkspace

3.       Using “Connect to Workspace” to download the workspace from the Git/SVN server.

4.       Delete C:\MyWorkspace and rename C:\MyWorkspace_temp back to C:\MyWorkspace

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.