PowerBuilder .NET Windows Forms applications do not currently support some features. Some are not implemented in PowerBuilder 11.0 and some have been partially implemented.
The tables in this chapter provide detailed lists of all objects, controls, functions, events, and properties and indicate whether they are supported
The following list summarizes support in Windows Forms for features in this release:
All DataWindow presentation styles are supported, but there are some restrictions on RichText and OLE presentation styles.
External function calls are supported except when the function has a reference structure parameter.
You cannot call functions on .NET primitive types that map to PowerBuilder primitive types. See Table 13-3 for the list of datatype mappings from .NET to PowerBuilder.
You can use the built-in Web services client extension (pbwsclient110.pbx) in applications that you plan to deploy to .NET Windows Forms. You cannot use any other PBNI extensions in a .NET target.
In-process OLE controls (controls with the extension .ocx or .dll) are partially supported. Most of the OLE control container’s events are not supported, but events of the control in the container are supported with the exception of the Help event. Other OLE features are not supported. You cannot create an ActiveX control dynamically, and you must set the initial properties of an ActiveX control in code because the implementation does not support saving to or retrieving from structured storage.
Support for OLE controls requires the Microsoft ActiveX Control Importer (aximp.exe). This tool generates a wrapper class for an ActiveX control that can be hosted on a Windows Form. It imports the DLL or OCX and produces a set of assemblies that contain the common language runtime metadata and control implementation for the types defined in the original type library. When you deploy the application, you deploy these assemblies. You do not need to deploy aximp.exe.
The aximp.exe tool is part of the .NET Framework 2.0 SDK, which can be freely downloaded from the Microsoft Web site. For more information, see “System requirements”.
The following features are not currently supported in .NET targets: shared objects, EAServer integration, COM/COM+ components, OLE automation server, data pipelines, tracing and profiling, DDE functions, and SSLCallback.
The .NET Framework replaces fonts that are not TrueType fonts, such as MS Sans Serif, with TrueType fonts. This replacement can cause unexpected display issues. For example, the cursor does not display when you click in an EditMask control that does not use a TrueType font. To avoid such issues, always use a TrueType font such as Tahoma.
