- Gary Eden
- PowerBuilder
- Friday, 6 November 2020 11:09 AM UTC
Hi,
I'm just starting to use the .net dll importer and it seems to do what I need it to do. I've now progressed to the next step of deploying the application. This is my first stumbling block as the application seems to be looking in the directory that the application is started in, it does not attempt to look in the path that we have all the PB 2019 dlls located and where i have placed the .net dll. I have managed to work around this by determining the assembly path at runtime and setting it in the of_createondemand. This has worked in a locally deployed application so should be fine however it feels a bit clunky.
I would just like to know if others have had this issue or am I doing something wrong that is creating this additional code requirement?
Thanks
Gary
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.