When you build & deploy a PowerServer project, the following happens:
-
Generate a PowerServer C# solution by copying templates from C:\Program Files (x86)\Appeon\Common\PSToolkit\[version]\NetBuild\AppTemplate.
-
Update the PowerServer C# solution by using the project painter settings (such as auth template, app name, Kestrel port, license, cache etc.).
-
Parse the DataWindow controls and DataStore objects and create PowerServer C# models.
-
Parse the embedded SQLs and create PowerServer C# models.
PowerServer Toolkit (installed at C:\Program Files (x86)\Appeon\PowerBuilder [version]\Pstools by default) converts the embedded SQLs and static DataWindows to PowerServer C# models (.cs files) and deploys them to the PowerServer C# solution > "AppModels" project > [appname] > "ESql" and "Models" sub-folders respectively.
-
Compile the PowerServer Web APIs from the solution.
-
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.
