PowerBuilder 2019 R3 Build 2703
I have an Azure Devops TFS source control containing the latest PowerBuilder 2017 source code.
I have PowerBuilder 2019 R2 Build 2703 migrated PBLs, containing a slighlty older version of the PB 2017 source code.
I want to do a full Get Latest, but it continually fails because Azure Devops is useless with large PowerBuilder projects.
So, for the first time ever I decided to take a look ar OrcaScript, and it looks good. I wrote this bat file:
REM Get everything from source control (Azure DevOps TFS)
"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\TF.exe" get "$/<MyProject>" /recursive /force
REM Put the objects we just got into the PBLs
orcascr190 /D runtime_version="188.8.131.5203" "_orca.txt"
REM Do a build
"C:\Program Files (x86)\Appeon\PowerBuilderCompiler 19.0\pbc190.exe" /d "<MyProject>.pbt" /o " <MyProject>.exe" /r "<MyProject>.pbr" /w y /f /m n /x 32 /bg y /p "<MyProjectName>" /cp "<MyCompanyName>" /de "<MyProjectShortName>" /cr "<MyCompanyName>" /v "<MyBuildNumber>" /vn "184.108.40.206" /fv "0 *this is not used nor is the Product version below*" /fvn "220.127.116.1103" /ge 0 /pd yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy /rt 18.104.22.16803
The OrcaScript script file contains this:
set debug true
scc set connect property logfile "OrcaBuild.log"
scc set connect property logappend "FALSE"
scc connect offline
; Tells the refresh to assume the source has already been
; extracted from TFS and to just import it
scc set target "<MyProject>.pbt" "refresh_all importonly"
; Perform the imports
scc refresh target "migrate"
Which works great, gets everything from TFS, appears to import it all in the PBLS, and does a build.
But when I open the worksapce in the PowerBuilder 2019 R3 IDE I am prompted with:
The PowerBuilder Runtime version of the current IDE has changed. Do you want to full build the application using the new PowerBuilder Runtime version?
If I select OK then a full build is done and all is good from that point on. But I just did a full build, I believe. So what am I missing? Is there an object that needs to be checked in after the migration from PowerBuilder 2017 to 2019 R3, as I thought it was just the PBLs that change during migration?
Any help gratefully recieved :) Thanks!