Known Issues for the WPF Runtime

You cannot use file-based system functions to embed non-image external resources in PowerBuilder code for a WPF target.

For example, if you change the build action of a text file from normal content to an embedded resource, the resource fails to load at runtime.

External Content resources for third-party controls (for example, the Microsoft WPF Image control) fail to load at runtime. Only embedded resources are loaded successfully at runtime.

In PowerBuilder .NET, the ToolbarMoved event is triggered for an SDI window only when you open the window.

The DatePicker and MonthCalendar controls display some dates in incorrect formats for culture settings other than en-us. Several of the format strings (MMMM, MMM, dddd, ddd, and tt) for the CustomFormat property of DatePicker controls are also incorrectly rendered in these culture settings.

The masks for enabling single-digit values for the hour in 12-hour or 24-hour formats (h and H) do not work properly. In PowerBuilder .NET, they work the same as the hh and HH masks, and always present hour values with two digits.

A runtime error occurs when you use the same name for an assembly and the WPF application that references the assembly.

Workaround: In a WCF Client Proxy project, do not name the generated assembly with the name of the WPF application that hosts the project.

Multiple-item selection in a ListView control is enabled when the ExtendedSelection property is set to true. However, in WPF applications, users cannot use the mouse to lasso the items they want to select.

Workaround: In WPF applications, users must hold down the Shift key to select multiple items.