If you do bootstrap full builds of your application, you can keep your source in an earlier version of PB and easily create a test exe in the new version. Allows you to test without committing to permanently moving the source code to the new PB version.
This is one and only line replaced in my command file to build exe into PB22 instead of PB19R3.
Using orca script to bootstrap from my SCC into PB 2022, full regen, and then build exe.
the commented out line uses orcascript 21 (from PB2021) to build using PB2019R3 runtime. The replacement line is all 2022 versions.
REM set orcarunvar=orcascr210 /D runtime_version="19.2.0.2728"
set orcarunvar=OrcaScr220 /D runtime_version="22.0.0.1878"
I then run several orcascripts using the orcarunvar:
%orcarunvar% buildfromsource.orca
%orcarunvar% buildexe.orca
I just released the last version of the STD Framework for PB / PS 2021 last week. However, all the retrofit code was added to this version in compliance with PB / PS 2022. So if you upgrade to this framework version, it will migrate & run properly in the new PB / PS 2022 GA as well. That includes both the 32bit & 64bit based native, PowerClient & PowerServer App's.
FYI: http://chrispollach.blogspot.com/2022/08/2022r2.html
Enjoy... Chris