Starting from Beta 3 (Version 2025 R2 Build 6373), features that previously supported .NET 6 and .NET 8 have been upgraded to support .NET 6, .NET 8, and .NET 10. To enable .NET 10 support, VC++ Runtime has also been upgraded (to version 2026).
Due to these changes, the following compatibility issues may occur:
-
Runtime switching issues within Version 2025 R2
Within the same PowerBuilder major version (for example, PB2025 R2 Beta 2, PB2025 R2 Beta 3), switching from a newer IDE to an older Runtime (that targets a lower .NET version) may cause runtime incompatibility or even IDE crashes.
The newer IDE uses .NET 10 to load certain runtime environment, and features such as ADO.NET database connection and .NET Assembly Calls also require the same .NET version to work. If an older Runtime (without the required configuration) is used, such features may not work properly.
Workaround:
After upgrade, if you want to use PowerBuilder IDE 2025 R2 Beta 3 (which supports .NET 6, 8, and 10) with an earlier PowerBuilder Runtime such as Beta 2 (which supports .NET 6 and 8), you will need to manually replace some files.
Manually copy the following files from the newer Runtime folder to the older Runtime folder (typically C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime [version]), so that both use the same .NET runtime configuration.
For 32-bit:
-
Appeon.DB.Proxy.runtimeconfig.json
-
pbdotnetinvoker.runtimeconfig.json
For 64-bit:
-
x64\Appeon.DB.Proxy.runtimeconfig.json
-
x64\pbdotnetinvoker.runtimeconfig.json
-
-
MSVCP140.dll errors in native client/server app
Native client/server applications may encounter the following MSVCP140.dll-related errors on some client machines. This issue currently only affects native C/S app.
Faulting module name: MSVCP140.dll, version: 14.36.32532.0, time stamp: 0x691de424
This is essentially caused by DLL loading priority and runtime version mismatch. To support .NET 10, PB2025 R2 upgrades VC++ Runtime (to version 2026) and the core DLL files (to version 14.50.x). However, the core DLL filenames (such as msvcp140.dll) remain unchanged. Due to the Windows DLL loading mechanism (see DLL Strict Mode), DLLs in the system directory (e.g., System32) have higher priority than those in the Runtime folder. As a result, the application may load an older version of the DLL from the system, causing incompatibility and crashes.
Solution:
Install the latest VC++ Runtime (such as version 2026) to ensure the system DLLs are up to date.
Alternatively, copy the following required VC++ Runtime DLLs from the Runtime folder to the same directory as the application executable file. This ensures the application directory takes precedence in DLL loading.
For 32-bit: vcruntime140.dll, concrt140.dll, msvcp140.dll
For 64-bit: vcruntime140.dll, vcruntime140_1.dll, concrt140.dll, and msvcp140.dll
After upgrade, .NET Desktop Runtime 10 must be distributed and installed to the client if your application uses features such as ADO.NET database connection. (Make sure the platform (32-bit or 64-bit) of .NET Desktop Runtime matches that of the application executable file.)
