-
Apoorva JUKANTI
- PowerBuilder
- Monday, 20 April 2026 05:45 PM UTC
Hi everyone,
I’m facing an issue with a 32-bit application that combines PowerBuilder and .NET components.
Our setup:
A PowerBuilder application invokes .NET DLLs.
We have two different applications installed on the same machine.
One application uses .NET Framework–based DLLs.
The other uses .NET 5–based DLLs.
Both applications include DLLs with the same names but different versions.
The problem:
Even though my PowerBuilder application references the correct (lower version, .NET Framework) DLLs from its own application folder, at runtime it seems to be loading the DLLs from the other application (.NET 5 version).
I’m unsure how DLL resolution works in this mixed PowerBuilder + .NET scenario, and why it’s not respecting the local application path.
Questions:
- What could cause a PowerBuilder application to load the wrong version of a .NET DLL?
- How does DLL resolution work in this context (PowerBuilder calling .NET)?
- Could this be related to GAC, PATH environment variables, or assembly binding?
- What’s the best way to isolate or enforce the correct DLL version?
- Any insights or suggestions would be really helpful.
Thanks in advance!
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.