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

Resolved PBNative Source Control Question

  1. Issue
0
Votes
Undo
  1. Mary Jane Foster
    Mary Jane Foster
  2. PowerBuilder
  3. Thursday, 28 March 2019 14:57 PM UTC

Hi:

I just migrated a PB12.1 application to a PB2017 R3 application.  When I click on the Library painter and select a .pbl, it shows me version numbers ranging in 1 to 18. 

Where are these version numbers coming from?  They are not in the .prp files and we don't work offline, so I would not expect them to be pulled from the .pbc files.  The assumption was that these would all have 1 as their Version Number.

I do not see a version anywhere in the .pbg files.

I want to clear up any misunderstanding I have as to where the version numbers come from.

Thank you!

Mary Jane Foster

 

Source Control Native
Conditional compilation
Responses (3)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 29 March 2019 15:00 PM UTC
  2. PowerBuilder
  3. # 1

Here is a .prp file:

0
2 03/29/2019 10:57:54

The version is the number before the check-in date

 

The source control provider must support the Ex version of action functions (SccCheckinEx/SccCheckoutEx) which is a Sybase extension, not part of the SCC API standard.

 

WizSource supports the Ex functions:

http://www.topwizprogramming.com/wizsource.html

 

Comment
There are no comments made yet.
Mary Jane Foster
Mary Jane Foster Accepted Answer Pending Moderation
  1. Friday, 29 March 2019 15:27 PM UTC
  2. PowerBuilder
  3. # 2

Hi Roland:

I apologize if my question was unclear.  

First, the source code control we use, is PBNative - we are not using a third party tool.

Post the migration the .prp file showed:

0
1 03/27/2019 16:43:08

When I looked at the same object in the Library Painter it showed version 6 - so if it is pulling from the .prp file, why are they showing two different versions post migration?  I hope this clarifies things a bit.

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 29 March 2019 19:03 PM UTC
  2. PowerBuilder
  3. # 3

The PBL file has a source control version table separate from the object directory. My guess is that the migration kept the source control version table intact.

The Check-In should update the version table in the PBL with whatever value is returned from the scc provider (PBNative in this case).

At some point did you start a different PBNative repository? That would explain them being out of sync.

 

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.