When the PowerBuilder application is deployed, make sure the following files are packaged and deployed with the .NET assembly DLL files:
-
PBDotNet.dll, PBDotNetInvoker.dll, PBDotNetCoreInvoker.dll, PBDotNetFrameworkInvoker.dll, Ijwhost.dll, and pbdotnetinvoker.runtimeconfig.json
To package the files automatically, select the ".NET Assembly Calls" option in the Runtime Packager so that the packager can automatically package the required files.
To package the files manually, go to the PowerBuilder Runtime location and get these runtime DLL files.
You will need to make sure the .NET assembly DLLs as well as any dependent DLLs are deployed in the same folder.
Note
PBDotNetInvoker.dll cannot be placed in more than one location at runtime, for example, if it is placed in both the runtime folder and the application root folder, the call to this file will fail (error "-52 -- The objectname is not registered." will be returned), because PBDotNetInvoker.dll in the runtime folder will be used for registration while PBDotNetInvoker.dll in the application root folder will be used (with higher priority) for PB callback functions; the file used for registration and call must be the same one, otherwise the call fails.
-
Universal CRT (C Runtime) and .NET Desktop Runtime, .NET Framework, or .NET Core
Make sure the target machine have Universal CRT (C Runtime) and .NET Desktop Runtime, .NET Framework, or .NET Core installed in order to run the .NET DLLs.
