• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Need help with Powerbuilder 2017R2 and subversion svn as a new developer

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Need help with Powerbuilder 2017R2 and subversion svn as a new developer

  1. How-to
0
Votes
Undo
  1. Daniel Seguin
    Daniel Seguin
  2. PowerBuilder
  3. Wednesday, 18 September 2024 20:59 PM UTC

Hello,

I need a bit of refresh of subversion - svn...

 

I am using Powerbuilder 2017R2 connect to subversion.

As a new developer, I had to get a working copy of another developer since in subversion we do not have the workspace, targets, and pebbles.

I have created a new folder called "Daniel DISIS - Working"

I have copied the contents from the other developer inside my folder

Then I opened PB2017R2, open workspace and select the workspace in the "Daniel DISIS - Working" folder 

Then I went to the option : add to source control

 

Then clicked ok, 

and PB came back with the screen below to add all files to source control.

So at this point, I did not click put the comment and clicked ok.

I did not change anything, and it is prompting me as if I had made a commit.

I just need some advice.

 

PowerBuilder R2 2022 cierra solo al abrir una vent...
How can Multi-select in DDDWs be done?
Responses (4)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 19 September 2024 02:28 AM UTC
  2. PowerBuilder
  3. # 1

Hi Daniel, Your version of PB is very old and it had very rudimentary support for SVN.  I recommend to you upgrade to PB 2022 R3 so you are on a supported version.  Please keep in mind some SVN operations you will need to do outside of the PB IDE using TortoiseSVN, such as branching.  

Comment
Daniel Seguin
  1. Daniel Seguin
  2. Thursday, 19 September 2024 02:36 AM UTC
Hi Armeen,



Yes exactly, that was my plan to migrate the customer to PB2022R3.

But since I just started this new project, my first task was to ensure I am able to support the current version.

My concern was that they PB2017R2 was unsupported and also running on windows 11 workstations.

Also, the customer is moving to Microsoft Devops Git soon. So another good reason to migrate to PB2022R3.



I have created the new branch within tortoise svn.



Do you see any issues with the new branch having the ws_objects folder vs the trunk which does not have ws_ojbects, and all the source objects are in the code folder?



Thanks



Daniel

  1. Helpful
There are no comments made yet.
Daniel Seguin
Daniel Seguin Accepted Answer Pending Moderation
  1. Thursday, 19 September 2024 02:01 AM UTC
  2. PowerBuilder
  3. # 2

When I looked at the copy received by the other developer, it was not version control as there was no .svn file

 

So I should create a branch from trunk to apply my changes

 

Finally the code got put into my branch related to my ticket 

 

 

Comment
Daniel Seguin
  1. Daniel Seguin
  2. Thursday, 19 September 2024 02:43 AM UTC
I am actually replacing the PB developer that is retiring soon

  1. Helpful
There are no comments made yet.
Daniel Seguin
Daniel Seguin Accepted Answer Pending Moderation
  1. Thursday, 19 September 2024 02:12 AM UTC
  2. PowerBuilder
  3. # 3

when looking inside my working folder associate to my new branch, I see this

 

But after doing my changes, I will want to merge my branch into trunk which looks like:

 

 

I think I did it the right way with a new branch and now I am seeing the ws_objects folder I am use to.

 

Can someone give me some advice.

 

Thanks

 

Daniel

 

Comment
Load more comments
Arnd Schmidt
  1. Arnd Schmidt
  2. Thursday, 19 September 2024 23:01 PM UTC
The ws_objects folder has Nothing to do with using branches or not.

I think you should read the document, especially what is written about:

"If you're familiar with how source control worked from PowerBuilder using MSSCCI you'll note a couple of significant differences in how it's handled under Subversion.

..

2. Under MSSCCI, only the target file and the exported source code was checked into source control. "

hth

Arnd

  1. Helpful
Daniel Seguin
  1. Daniel Seguin
  2. Thursday, 19 September 2024 23:34 PM UTC
I know, not using branches was not related to ws_objects.

ws_objects is generated by Pb when we go to the workspace, and add to version control, and choose the repo (either the trunk or branch)

They are using subversion svn and not MSSCCI as the pbg files were around 10 years old.

Like I said before I will doing an upgrade to PB2022R3 and doing some cleanup to reduce confusion.



Thanks for you help.



Daniel



  1. Helpful
Arnd Schmidt
  1. Arnd Schmidt
  2. Thursday, 19 September 2024 23:51 PM UTC
Okay,

then a "Happy cleanup and merging".

Remember that "pre PB 2017" SVN was used via an MSSCCI Provider and there was no ws_folder structure.

https://github.com/OpenSourcePFCLibraries/12.6

vs.

https://github.com/OpenSourcePFCLibraries/2019

regards

Arnd
  1. Helpful 2
There are no comments made yet.
kitty he @Appeon
kitty he @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 25 September 2024 01:59 AM UTC
  2. PowerBuilder
  3. # 4

Hi Daniel, 

The features supported in the PB2017R2 version are limited, which means your first step was incorrect. 

Your application is already on the SVN server, so what you need to do is connect to the workspace instead of copying someone else's application and then adding it to source control. 

 

I recommend you take a look at the PB help documentation for more information. 

https://docs.appeon.com/pb2022r3/pbug/Using_SVN_source_control_system.html#svn_get

 

Regards, 

Kitty

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.