Learn about known issues and apply workarounds for third-party and custom controls in PowerBuilder.
| CR# | Description |
|---|---|
| 673839 | Updatable columns listbox malfunctions when the list of columns is larger than what fits on one screen. For example, open the Update Properties dialog for the listbox. In the Updatable Columns listbox, select the ID column: this is now unselected and the columns are selected. Scroll down and then back up: more items are unselected. And so on. |
| 640523 |
WPF Publish SmartClient application fails when third-party controls are included. If a WPF application includes third-party controls and the required reference assembly files are not in a build subfolder (..\bin\Debug or ..\bin\Release), when you publish it as a SmartClient application the publish does not copy related files to the publish folder (..\bin\Debug\published or ..\bin\Release\published). Workaround: Copy all required assembly files to the build subfolder (..\bin\Debug or ..\bin\Release) according to the section <ReferenceAssemblyFiles> of the publish.xml (also in the build subfolder). The publish is then successful. |
| 635007 | XAML best practices for third-party controls. Define the third-party namespaces in the XAML root element before adding third-party controls. If you do not, an incorrect namespace is added inline and causes XAML namespace errors. |
| 633431 | Sometimes a new Toolbox tab that you added will disappear. If you add a new tab to the Toolbox and then PowerBuilder .NET crashes, the new tab is not saved. |
| 626856 |
Using third-party controls that refer to different versions of WPFToolkit.dll causes build error.
The WPFToolkit.dll (version 3.5.40320.1), referenced by WPF applications in PowerBuilder .NET, is added automatically. If you use other third-party WPF controls that reference different versions of WPFToolkit.dll, you see the build error "The located assembly's manifest definition does not match the assembly reference." |
| 621554 |
Double-clicking some third-party controls does not open the Script view.
The Script view does not open automatically when you double-click some third-party controls, such as RadCalendar, in a Layout view. This issue also exists in Visual Studio. Workaround: Open the Script view for the window or parent control and select the third-party control from the top left drop-down list. |