The WPF Window Application wizard in PowerBuilder .NET provides an option for converting a standard PowerBuilder Classic client/server or a Windows Forms target to a WPF Window Application target. The .NET Assembly wizard in PowerBuilder .NET provides an option to convert a PowerBuilder Classic .NET Assembly target.
After you select these conversion options and click Finish, the wizards automatically migrate the PowerBuilder Classic targets you select. However, you may still need to manually refactor some applications after you convert them.
This table lists some of the features that require special attention after you migrate applications from PowerBuilder Classic. Topic references in the table are to the PowerBuilder .NET Features Guide.
| Feature | Effect of migration |
|---|---|
| Accelerator characters | Ampersand (&) changed to underscore (_). See Accelerator Characters in Control Labels. |
| Conditionalized (preprocessor) code blocks | Invalid code blocks for PowerBuilder .NET are maintained, but ignored. See Conditional Compilation in PowerBuilder .NET Targets. |
| Control handles | Controls nested in windows do not have their own handles. See Modified and Unsupported Features in PowerBuilder .NET . |
| Dashes in identifiers | Dashes are replaced with a string you can select in the target wizard. See Coding Restrictions. |
| Event sequence | May require manual refactoring. See Modified and Unsupported Features in PowerBuilder .NET . |
| GroupBox controls | Controls that are inside a GroupBox belong to the GroupBox, not to the container of the GroupBox. See Semantic Differences. |
| Large application migration | May cause OutOfMemory error. Turn on 3G switch to avoid this error. See Memory Tuning for Large Applications. |
| Menu and toolbar styles | Maintained from PowerBuilder Classic. If you migrate PowerBuilder applications earlier than 11.0, menus and toolbars use traditional styles. See Selecting a Toolbar Style and Menu Styles in PowerBuilder .NET. |
| Non-TrueType fonts | Visible at design time, but replaced at runtime. See Modified and Unsupported Features in PowerBuilder .NET . |
| Pipeline and Query objects | Imported, but ignored at runtime. See Modified and Unsupported Features in PowerBuilder .NET . |
| Resource files | Resource directories that you select in the wizard are copied relative to the new target path, based on the relative path to the original target. See Adding Resources to a Target and Project Painter User Interface. |
| Skins | Default skins are attributed to migrated applications. See Skin Selection for Applications and Controls. |
The WPF Application includes migration options for applications with dashes in identifiers and with right-to-left formatting. If you click Finish before making a migration option selection, the wizard migrates the application using default settings for these options.