Powerbuilder Documentation 12.0

Powerbuilder Documentation 12.0

  2. Powerbuilder Documentation 12.0

Unsupported Properties for Controls in Windows Forms – PB Docs 120

Unsupported Properties for Controls in Windows Forms If your application uses unsupported properties for Windows Forms targets, you must rework the application before you deploy it. This table is an alphabetical listing of unsupported properties. It also indicates the controls on which they are not supported, and any notes that apply to specific controls. Unsupported…

Powerbuilder Documentation 12.0 PB Docs 120 Powerbuilder Documentation Powerbuilder Documentation 12.0 Powerbuilder Documentation Older Powerbuilder Web Targets Guide

Incremental Builds – PB Docs 120

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…

Powerbuilder Documentation 12.0 PB Docs 120 Powerbuilder Documentation Powerbuilder Documentation 12.0 Powerbuilder Documentation Older Powerbuilder Web Targets Guide

Troubleshooting Deployment Errors – PB Docs 120

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 PBNET_HOME system environment variable is set to…

Powerbuilder Documentation 12.0 PB Docs 120 Powerbuilder Documentation Powerbuilder Documentation 12.0 Powerbuilder Documentation Older Powerbuilder Web Targets Guide

System Requirements for .NET Windows Forms Targets – PB Docs 120

System Requirements for .NET Windows Forms Targets You must install version 2.0, 3.0, or 3.5 of the Microsoft .NET Framework on the same computer as PowerBuilder. For intelligent update applications, you must also install the .NET Framework 2.0, 3.0, or 3.5 SDK (x86). Make sure that the system PATH environment variable includes: The location of…

Powerbuilder Documentation 12.0 PB Docs 120 Powerbuilder Documentation Powerbuilder Documentation 12.0 Powerbuilder Documentation Older Powerbuilder Web Targets Guide

Resources and Other Required Files – PB Docs 120

Resources and Other Required Files All resource files must be relative to the path of the .NET Windows Forms target. Click Add Files on the Resource Files page of the project painter to select image files that your application requires. PowerBuilder .NET Windows Forms applications do not support PBR files, and they are unable to…

Powerbuilder Documentation 12.0 PB Docs 120 Powerbuilder Documentation Powerbuilder Documentation 12.0 Powerbuilder Documentation Older Powerbuilder Web Targets Guide

Intelligent Deployment and Update – PB Docs 120

Intelligent Deployment and Update One of the features of .NET smart client applications is that they can be deployed and updated from a file or Web server using Microsoft .NET ClickOnce technology, making it easier for users to get and run the latest version of an application and easier for administrators to deploy it. PowerBuilder…

Powerbuilder Documentation 12.0 PB Docs 120 Powerbuilder Documentation Powerbuilder Documentation 12.0 Powerbuilder Documentation Older Powerbuilder Web Targets Guide

HasFileManager – PB Docs 120

HasFileManager Set this property to false to hide the File Manager on a particular page in a Web Forms application. Applies to Window controls Usage In scripts, surround the HasFileManager property in a conditional compilation code block for Web Forms applications:

This property is valid for .NET Web Forms applications only when the PBFileManager…

Powerbuilder Documentation 12.0 PB Docs 120 Powerbuilder Documentation Powerbuilder Documentation 12.0 Powerbuilder Documentation Older Powerbuilder Web Targets Guide

Application Directory Permissions – PB Docs 120

Application Directory Permissions When you deploy a new Web Forms target, a temp directory is created in the Inetpubwwwrootapplication_name directory, where application_name is the name of your application, and several subdirectories are created in the Inetpubwwwrootapplication_name_root directory. Files are written to and deleted from these directories, therefore the IIS_IUSRS group must have full permissions on…

Powerbuilder Documentation 12.0 PB Docs 120 Powerbuilder Documentation Powerbuilder Documentation 12.0 Powerbuilder Documentation Older Powerbuilder Web Targets Guide

HasPrintManager – PB Docs 120

HasPrintManager Set this property to false to hide the Print Manager on a particular page in a Web Forms application. Applies to Window controls Usage In scripts, surround the HasPrintManager property in a conditional compilation code block for Web Forms applications:

This property is valid for .NET Web Forms applications only when the Print Manager…

Powerbuilder Documentation 12.0 PB Docs 120 Powerbuilder Documentation Powerbuilder Documentation 12.0 Powerbuilder Documentation Older Powerbuilder Web Targets Guide

WebPermission – PB Docs 120

WebPermission WebPermission settings are required for features and functions in .NET targets. The WebPermission class belongs to the System.Net namespace described on the Microsoft Web site at http://msdn.microsoft.com/en-us/library/system.net.aspx. WebPermission required in .NET targets Function or feature Permission required GetURL (Inet function) Connect for urlname argument PostURL (Inet function) Connect for urlname and serverport arguments Web…

Powerbuilder Documentation 12.0 PB Docs 120 Powerbuilder Documentation Powerbuilder Documentation 12.0 Powerbuilder Documentation Older Powerbuilder Web Targets Guide