1. Herbert Hader
  2. PowerBuilder
  3. Wednesday, 15 November 2023 17:35 PM UTC

Hello everybody,

finally we can start migrating some applications built with PB 12.5 to PB 2022 R2!

Now I think about how to migrate - or create newly - the working copies, one for each app. We already had started to work with SVN repositories using the AgentSVN interface. We have one repo for each app plus one shared repo. Workspace files were not added yet to the app repo's. The app repo's all have the same structure: A single target file in the root and a Sub-Dir for each PBL, but PBL's itself were not committed of course. Each sub dir contains a PBG file, rather. In addition: All working copies point to that shared repo by using some svn:externals properties. - That setup worked all fine, but of course we want PB's builtin SVN interface now.

Now I'd appreciate advice on how to start. I see I can create a new workspace inside an app's working copy - add the target - add the workspace to source control - but at that point I'm not sure if I should proceed as PB announces it would store the complete working copy in a new "folder with the workspace name" - I would not like that very much. Is there a more flexible way?

And in general: Does PB support that "externals" property at all?

Further: Some picture files are part of the qpplications. We had managed to keep them in the same repo's using Tortoise . Will PB tolerate Tortoise operations executed against the same repo's he manages it's application in?

Would be great if someone could provide advice on that. Thanks!

 

 

 

Herbert Hader Accepted Answer Pending Moderation
  1. Monday, 20 November 2023 14:24 PM UTC
  2. PowerBuilder
  3. # 1

Does one of you work successfully with PB2022R2 and AgentSVN? After installation I do not see the choice to select that PBSCC provider in the "add to source control" dialog at all (Windows 10).

I know it is not (yet?) approved to work with PB2022R2.

Thank you!

Comment
  1. Herbert Hader
  2. Monday, 20 November 2023 22:10 PM UTC
Thank you Arnd! Only choice for "source control system" in "properties of workspace" is "PB native". Only choices for "add to source control" are "Git" and "SVN". (Example workspace is new, content is extremely simple)
  1. Helpful
  1. Arnd Schmidt
  2. Monday, 20 November 2023 22:49 PM UTC
Can you start PowerBuilder PB 12.5 on the same machine and does this version recognize Agent SVN?

https://power2build.wordpress.com/2014/05/27/powerbuilder-and-source-code-control-scs/
  1. Helpful
  1. Herbert Hader
  2. Tuesday, 21 November 2023 10:15 AM UTC
Thanks again, Arnd. Following Jussi's hint I have installed the 32bit flavour of AgentSVN in addition now - and now I can select it in PB's workspace config dialog. So - let's give it a try.
  1. Helpful
There are no comments made yet.
Herbert Hader Accepted Answer Pending Moderation
  1. Friday, 17 November 2023 15:45 PM UTC
  2. PowerBuilder
  3. # 2

OK! Thanks for reading. I've read some more, in particular https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/182-powerbuilder-2017-r2-new-feature-subversion-svn-source-control-support (thanks again, Bruce!). So I see, PB goes it's own way - I'll have to rebuild all repositories - I see no support for svn:externals - I see no other great solution for code shared between workspaces. But maybe I missed something yet.

Should I stay with AgentSVN if possible?

 

Comment
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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.