Known Issues for the WPF Debugger

If you set a breakpoint immediately prior to a FOR...NEXT statement, then issue successive Step Into commands, the WPF Debugger cursor stops twice at the line with the FOR clause.

Some expressions that appear correctly in PowerBuilder Classic applications are not included, or appear incorrectly, in PowerBuilder .NET QuickWatch and Watch windows. These include external function calls and some DataWindow functions.

Temporary variables that do not exist in the application code (for example, __PB_TEMP_DB__OutputVars0), may appear in some debugger windows.

Workaround: You can safely ignore these temporary variables.

The debugger sometimes selects multiple lines when it should select a single line, such as when you set a breakpoint in a CHOOSE CASE statement.

The QuickWatch window displays some CheckBox control properties incorrectly.

Debugger functions are not available for applications that are in release mode. For example, if you attempt to step into an application in release mode, the debugger opens a C# file and stops in the C# file.

Workaround: Change your project's build type to debug.

In some debugger windows, you can select a breakpoint and use the Go To Source Code command to open the source code at that breakpoint. This command works incorrectly for a breakpoint in a PowerBuilder .NET workspace that has multiple PowerBuilder .NET targets.

The debugger incorrectly displays zero-based object arrays used by some Web services.