Compilation process
When you build & deploy a PowerServer project, the following
happens:
-
Generate a PowerServer C# solution by copying templates from
C:Program Files
(x86)AppeonCommonPSToolkit22.0NetBuildAppTemplate. -
Update the PowerServer C# solution by using the project
painter settings (such as auth template, app name, Kestrel port,
license, cache etc.). -
Compile the PowerServer Web APIs from the solution.
-
Parse the DataWindow controls and DataStore objects and
create C# models. -
Parse the embedded SQLs and create C# models.
PowerServer Toolkit (installed at C:Program Files
(x86)AppeonPowerBuilder 22.0Pstools by default) converts the
embedded SQLs and static DataWindows to C# models (.cs files) and
deploys them to the PowerServer C# solution > “AppModels”
project > [appname] > “ESql” and “Models” sub-folders
respectively. -
Analyze PowerScripts for unsupported features.
-
Build the PBLs and re-generate the PBD files.
-
Split the PBD files at object level.
-
Uploads the runtime files, cloud app launcher, application
files (PBD files, app executable file, external files etc.), and
the compiled Web APIs to the server.
When you deploy a PowerServer project, the following
happens:
-
Update the PowerServer C# solution by using the project
painter settings (such as auth template, app name, Kestrel port,
license, cache etc.). -
Compile the PowerServer Web APIs from the solution.
-
Uploads the runtime files, cloud app launcher, application
files (PBD files, app executable file, external files etc.), and
the compiled Web APIs to the server.