- Les Kaplan
- PowerBuilder
- Wednesday, 2 March 2022 04:23 PM UTC
Hello,
So we migrated to PowerBuilder 2019 and the previous version called a .Net Dll 4.52 framework. I followed all the instructions to import to a NVO that calls the dll and set the assembly to a direct path that everyone has as well as the one that lives with the folder in the app, so I tried it both ways. I can run the application remotely, but none of my users can call the dll from the PowerBuilder application. The connection to the dll returns a -3 for them. I have added all the required dlls for .net that was in the instructions and made sure we had all the frameworks were installed, including the C runtime.
Can you tell me am I missing something here? Any information would be appreciated.
Here are the instructions I followed without any luck with my users:
When the PowerBuilder application is deployed, the system DLLs such as PBDotNet190.dll, PBDotNetFrameworkInvoker190.dll, and PBDotNetCoreInvoker190.dll will be deployed automatically. However, you will need to make sure the .NET DLLs as well as any dependent DLLs are deployed in the same folder.
And also make sure the target machine have Universal CRT (C Runtime) and the required .NET Framework or .NET Core installed in order to run the .NET DLLs.
Thanks,
Les Kaplan
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.