The project must be deployed and run successfully before it can be debugged with PowerClient Debugger, because:
-
The application executable (to be more exactly, the PBD files) will be debugged by the PowerClient Debugger, therefore, if you have changed the application scripts, make sure to deploy the application again immediately, so that the scripts in the PBD files exactly match with the scripts in the painter.
-
When you insert breakpoints in the scripts in the painter, the breakpoints will be mapped to the corresponding scripts in the PBD files.
-
Whether to debug the project as 32-bit or 64-bit should be configured in the platform setting in the PowerClient project painter > General tab before the project is deployed.
-
It is recommended that you run the application before starting PowerClient Debugger, so that the cloud app launcher can be downloaded and installed. If the cloud app launcher is not installed, PowerClient Debugger will open the browser for you to install the cloud app launcher first.
To start the PowerClient Debugger, click the Debug Project button (
) in the PowerClient Toolbar.
The PowerClient Debugger has the same toolset as the PowerBuilder Debugger. You can insert breakpoints, step in/over/out the scripts, add/remove watch, and use quickwatch, exactly in the same way as PowerBuilder Debugger. For detailed instructions, refer to Debugging an application in PowerBuilder User Guide.
