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

Resolved Best practice to share code across workspaces?

  1. How-to
0
Votes
Undo
  1. John Raghanti
    John Raghanti
  2. PowerBuilder
  3. Tuesday, 21 July 2020 16:32 PM UTC

Hi,

I've got 2 workspaces and use Microsoft VSS for source control.

I'm looking to add a set of visual and non-visual objects that I'd like both workspaces to use. 

What's the best way to do this?

Can we just create a PBL and reference it in both? How would VSS handle this?

Should we create a new target and put that target into both workspaces?

Something else I haven't thought of?

Thanks!

Right Indent Value in Powerbuilder RTE control
google api send email
Responses (3)
mike S
mike S Accepted Answer Pending Moderation
  1. Friday, 8 January 2021 20:14 PM UTC
  2. PowerBuilder
  3. # 1

another approach:

Use the PBL(s) ONLY in the target responsible for maintaining it.

In the other app(s), just include the PBD in the library list instead of the PBL.  That ensures you only modify it from the one app and only have it under SCC in the one app.

 

 

Comment
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 8 January 2021 19:34 PM UTC
  2. PowerBuilder
  3. # 2

Hi John, Any non-visual code that should be shared across multiple apps would be best you deploy as REST APIs and maintain a single project for that server code rather than duplicate.  The PowerSript Migrator, which is included in the PB CloudPro bundle, will automatically convert your non-visual code to REST API.  Here is more info: https://www.appeon.com/products/powerscript-migrator

Comment
There are no comments made yet.
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Friday, 8 January 2021 18:07 PM UTC
  2. PowerBuilder
  3. # 3

Hi John,

 

Yes, for previous MS VSS you could just create a PBL and use it in both Workspaces.

 

Just wondering, have you tried out Git instead of the now EOL MS VSS? I personally like MS VSS quite a lot, but unfortunately it's out of support. That's why many are now using the new features of Git/SVN Source Control on the latest versions of PowerBuilder.

 

Regards,

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.