When you deploy the core PowerBuilder runtime files, you must ensure that the msvcr71.dll and msvcp71.dll Microsoft Visual C++ runtime libraries and the Microsoft .NET Active Template Library (ATL) module, atl71.dll, are present on the user’s computer or server. The PowerBuilder runtime files have a runtime dependency on these files and they are required for all applications and components that require the PowerBuilder runtime. You can obtain these DLL files from the DLL archive Web site. They are also available from the DLL archive Web site.
The PowerBuilder runtime files also have a runtime dependency on Microsoft Windows GDI+ (gdiplus.dll). PowerBuilder .NET targets cannot be launched if gdiplus.dll is not available on the system. GDI+ is the subsystem of the Windows XP or Windows Server 2003 operating system that implements enhanced graphic capabilities for screens and printers. It is included with Windows Vista but it is not part of the Windows 2000 operating system, therefore if you deploy your PowerBuilder application to Windows 2000, you must make sure that gdiplus.dll is available on the target computer and in the system path. GDI+ can be downloaded from the Microsoft Web site.
Files must be installed before running MSI file
Some files installed by the MSI file generated by the PowerBuilder
Runtime Packager have dependencies on these files. For example, atl71.dll and gdiplus.dll must
be installed on the user’s computer before the pbjvm115.dll file
can be registered. Make sure these files are on the target computer
before you run the MSI file generated by the Runtime Packager.
Microsoft.Ink, Microsoft.Ink.dll, and Microsoft.Resources.dll are required if your application uses InkEdit and InkPicture controls. These files are part of the Microsoft Windows XP Tablet PC Edition Software Development Kit 1.7, which is available on the Microsoft Web site.
Microsoft has discovered some incompatibility issues between these DLLs and the .NET Framework 2.0. You can obtain an update to address these issues from Microsoft.
PowerBuilder applications can use DirectX 3D rendering to display 3D graphs (Pie3D, Bar3D, Column3D, Line3D, and Area3D) with a more sophisticated look. You can use data item or series transparency with the DirectX graph styles to improve the presentation of data.
The DirectX 3D rendering depends on the DirectX runtime. The first time you select the Render3D check box on the General tab of the Properties view for a 3D graph, PowerBuilder launches the DirectX installer. If you opt out of the installation, the Render3D property is ignored. End users of PowerBuilder applications must also have the DirectX runtime installed on their computers to view the DirectX graph styles. You can download a redistributable package containing the DirectX runtime from the Microsoft Web site
For computers with older graphics drivers, you can check whether DirectX is supported by running dxdiag.exe. This file is typically installed in the Windows\System32 directory. The Display tab of the DirectX Diagnostic Tool that opens when you run dxdiag.exe indicates whether Direct3D is enabled.
PowerBuilder uses AJAX (Asynchronous JavaScript and XML) update functionality for Web Forms applications. With ASP.NET AJAX, the page is updated by refreshing individual regions of the page asynchronously.
Although PowerBuilder .NET Web Forms and .NET Web Service component targets work with .NET Framework 3.5, they do not use the version of AJAX that installs with .NET Framework 3.5. You must install AJAX Extensions version 1.0 (build 61025.0) for these .NET target types.
Because PowerBuilder uses the AJAX update feature by default, AJAX extensions are required for Web Forms applications on all development and deployment machines. You can download and install the Microsoft ASP.NET AJAX Extensions version 1.0 from the ASP.NET Web site.
