@Francisco,
Hi,
There's some confusion going on, please see:
https://community.appeon.com/index.php/qna/q-a/pb-2022-r2-net-6?limitstart=0#reply-42155
and quoting Peter Pang:
"PB2022 R2:
DLL of .Net framework/.Net Core/.Net x(5,6) can be imported by using .NET DLL Importer. Because it is forward compatible, the original distinction option has been removed.
But after being imported, the LoadWithDotNet function is used by default, which can load normally. If you are worried about compatibility problems, you can also manually change to LoadWithDotnetFramework.
https://community.appeon.com/index.php/qna/q-a/snapdevelop-powerbuilder-net-confusion
"
It's really a shame if .Net Framework DLLs would stop to work, since not all is easily convertible to .Net, especially if you have third party libraries.
Some of our stuff is easily converted and other things are nearly impossible unless we hire some kind of an expert, making migration more difficult and expensive..
regards
https://stackoverflow.com/questions/3490327/assembly-binding-redirect-does-not-work
and maybe you can get more information by running "fuslogvw.exe" or this tool that is a better version of it: https://github.com/awaescher/Fusion
good luck!
In our case, since the PB application is the calling application and there is no config file, not sure how to do it.
Can I get any support from Appeon team on this?