Project Painter User Interface

Use the Project painter to generate compiled resources—such as EXE and .NET assembly files—for runtime applications and components.

You can also locally execute the generated files from the design time environment by selecting Run from the Design menu of the Project painter, or from target or project context menus in the Solution Explorer. For WCF Client Proxy projects, you can select Generate Proxy from the Design menu of the Project painter, or from the project context menu.

The PowerBuilder .NET Project painter displays horizontally stacked tabs separating functional areas of a Project object rather than the PowerBuilder Classic painter style that uses top row tabs.

The options for full and incremental builds are not included on the General tab of the Project painter as in PowerBuilder Classic. Instead, you can specify the build scope by selecting Full Build or Incremental Build from the target and project context menus in the Solution Explorer. You can also select the build scope for the current target from the Build menu, or for the current project from the Design menu of the Project painter. If you open a WPF project, the WPF Project Painter Toolbar provides options for building and debugging the project, as well as checking dependencies between output assemblies.

The Resources tab in the Project painter for PowerBuilder Classic is not available in PowerBuilder .NET. Instead, you add resources to a target from a context menu in the Solution Explorer, or in the wizard when you create the target. The build process copies resource files to the project output directory.

PowerBuilder .NET does not use PBD files, so the Library Files tab in the Project painter has only a list box for Win32 dynamic library files; it does not have a separate list for PowerBuilder library files. Although Windows Forms projects in PowerBuilder Classic require PBD files for applications with DataWindow, Query, or Pipeline objects, when you migrate a Windows Forms target to PowerBuilder .NET, the list of PowerBuilder library files on the project's Library Files tab is not processed during the migration.