Performance suggestions on project compilation and deployment

It is normal behavior that the PowerServer Toolkit would take 3 to 4 times as long as a normal compile. There is much additional work to do, including:

  • Obtaining database schema for the conversion;

  • Converting DataWindows to C# models and static SQLs to C# properties;

  • Breaking down all PBD files granularly into each individual object/definition file;

  • Encrypting compiled files;

  • Deploying the files to the web server, or packaging the files, etc.

There are a few tips for you to speed up the process:

  • Use the local machine as the development environment. This means that you set up the Web server, PowerServer, and database server on the local machine, and the database server type and version shall be the same as the one to be used in the production environment.

  • Make sure that the option "During compilation, report unsupported PowerScript features for PowerServer deployment" is selected in the application additional properties. The unsupported features report can help you quickly locate and fix problems related with PowerServer deployment.

  • You need not sit and wait for the whole process to finish. It is possible to build the PowerServer projects through scripts (see Tutorial 7: Building your PowerServer project with commands).