64-Bit WPF Application Deployment
You can deploy PowerBuilder� .NET WPF applications on 32-bit and
64-bit systems.
Through a new platform option in the WPF project, you can create PowerBuilder
applications that deploy on 32-bit and 64-bit systems. The default value is
“32-bit.”
You can set the Platform Target build option to “32-bit” or “32-bit or 64-bit.” The
latter option runs as a 32-bit application on 32-bit platforms and a 64-bit application
on 64-bit platforms.
Other targets�WCF Service, PB Assembly, .NET Assembly�are all callees, so the application
type determines the running mode. You cannot select the platform; they build as “AnyCPU”
mode.
Compilation
Depending on the Platform Target setting, the application compiles in
different ways.
- 32-bit (default) � compiles the application or assembly to run by
any 32-bit, x86-compatible common language runtime. - 32-bit or 64-bit � compiles an application or assembly that runs
on any Windows platform.
Microsoft uses the names “x86” and “AnyCPU.”
Performance
64-bit deployment gives you an interface in which to develop
different types of applications, especially applications for 64-bit Windows
platforms. This kind of application can use more than 4GB of RAM.
Limitations in 12.5.1
Some PowerBuilder features are not available when running a “32-bit
or 64-bit” application on a 64-bit platform.
- 64-bit PB WPF application does not support the debugger.
- These features are not supported in 64-bit PB WPF applications:
- The OLE-related objects, such as PBOmObject,
PBOleObject, PBOmControl, PBOleControl, and PBOleCustomControl - PBMailSession
- Some string functions that end with “A”, such as
FillA(), LeftA(), LenA(), MidA(), PosA(), ReplaceA(), and RightA() - Read PSR files and save data in Excel 8 format in
DataWindow - Non-ADO.NET drivers
- MobiLink synchronization
- InkEdit feature in DataWindow
- The OLE-related objects, such as PBOmObject,
- For WCF WebService projects, compiled assemblies behave like WPF
assemblies. They are compiled using AnyCPU mode. If a WCF WebService references
32-bit libraries or assemblies, configure the hosting IIS or application pool as
“Enable 32-bit application.” Once configured like this, IIS runs on x64
environments in WOW64 mode. That means the IIS or application pool runs as WOW64
mode, so it can hold 32-bit Web services.
Error Messages and Runtime Exceptions
The most common exception caused by this feature is
BadImageFormatException, which is thrown when the file image of a dynamic link
library (DLL) or an executable program is invalid.
| Main Application Format | Platform | Format of the Assemblies Loaded at Runtime |
Remarks |
|---|---|---|---|
| 32-bit | 32-bit | 32-bit, 32-bit or 64-bit | |
| 32-bit | 64-bit | 32-bit, 32-bit or 64-bit | WOW64 |
| 32-bit or 64-bit | 32-bit | 32-bit, 32-bit or 64-bit | |
| 32-bit or 64-bit | 64-bit | 64-bit, 32-bit or 64-bit |
The main application determines the runtime environment in the entire
application life cycle. This exception is raised when the format of an assembly
conflicts with the format of main application at runtime.