Troubleshooting Runtime Errors – PB Docs 150
Troubleshooting Runtime Errors If a .NET application or component produces unexpected errors, make sure that the PowerBuilder runtime files on the target computer or server have the same version and build number as the PowerBuilder files on the development computer. Parent topic: Troubleshooting .NET Targets Document get from Powerbuilder help Thank you for watching.
Incremental Builds – PB Docs 150
Incremental Builds Incremental builds allow you to save time while deploying applications for testing or production purposes. For incremental builds, only object classes that are affected by one or more changes are recompiled during the build process. Target level The incremental rebuild process for .NET targets is conducted as the first step of a project�s…
Best Practices for .NET Projects – PB Docs 150
Best Practices for .NET Projects Although PowerScript is essentially a compiled language, it is quite tolerant. For the sake of performance, the PowerBuilder .NET compiler is not designed to be as tolerant as the PowerBuilder native compiler. To be able to compile your applications with .NET, you should avoid certain practices in your PowerScript code….
Attaching to a Running Windows Forms Process – PB Docs 150
Attaching to a Running Windows Forms Process For Windows Forms projects, you can start your deployed application from its executable file before starting the debugger, and then attach to the running process from the debugger. To attach to a process that is already running: In the Project painter, select Run > Attach to .NET Process….
Build and Deploy Directories – PB Docs 150
Build and Deploy Directories When you deploy a .NET application project, PowerBuilder creates a build directory under the directory for the current target. The name of the build directory is TargetName.pbt_build, where TargetName is the name of the current target. If the project you deploy has a debug build type, the build files are generated…
PowerBuilder New Features 12.5.1 – PB Docs 150
PowerBuilder New Features 12.5.1 This help describes significant features introduced in the 12.5.1 release of PowerBuilder .NET. Document get from Powerbuilder help Thank you for watching.
Using the Connection Object – PB Docs 150
Using the Connection Object Build a .NET client application for an EAServer component using the Connection object. Use the Template Application target wizard to create a client application, then use a .NET application wizard to create a .NET target using the library list and application object of the target you just created. Alternatively, use a…
Triggering Build and Deploy Operations – PB Docs 150
Triggering Build and Deploy Operations PowerBuilder lets you trigger build and deploy operations when you run or debug a Windows Forms project. By default, when you click the running man or debugging icon in the PowerBuilder toolbar, or select Run from a project menu or context menu for one of these target types, PowerBuilder determines…
Connections Using the JaguarORB Object – PB Docs 150
Connections Using the JaguarORB Object To create a CORBA-compatible client, you can use the JaguarORB object instead of the Connection object to establish the connection to the server. The JaguarORB object allows you to access EAServer from PowerBuilder clients in the same way as C++ clients. Two techniques The JaguarORB object supports two techniques for…
Troubleshooting Deployment Errors – PB Docs 150
Troubleshooting Deployment Errors The deployment process has two steps: the PowerBuilder-to-C# emitter (pb2cs) runs, then the project is compiled. Errors are written to the output window, and the progress of the deployment process is written to the DeployLog.txt file. PB2CS errors If pb2cs fails, make sure that: The pbc2cs.exe file is present in the PowerBuilder…