1. Don Olliver
  2. PowerBuilder
  3. Wednesday, 5 June 2019 17:44 PM UTC

We are experiencing an issue with multiple PB 2017 .NET assembly DLL versions and their associated PBD files.

From what we have determined, the .NET assembly DLL does not look in its own folder for the PBD file. To make the location lookup succeed, we have to add the folder to the machine's PATH environment variable. 

This creates a problem for multiple version installs. If we add each install folder to PATH, the DLL could find the wrong PBD file version. It's possible we might work around the issue by renaming the PBD file to include the associated version. However, that means renaming the .PBL library (since the PBD gets its name from the PBL name), as well as modifying the target library list and the assembly project object.

Is there a recommended way in PB 2017 to specify the associated PBD file name for a .NET assembly DLL?

Regards,

Don Olliver

Accepted Answer
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Thursday, 6 June 2019 07:53 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Don,

 

PB has never supported this feature. You may try to directly read the PBD/DLL file and implement what you want by identifying the time being used to compile its attributes or the file size.

 

Regards,

Mark Lee

Comment
There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Friday, 7 June 2019 14:58 PM UTC
  2. PowerBuilder
  3. # 1

Have you tried adding " . ; "  to the front of PATH - or front of APPPATH (registry setting) to avoid impacting other apps?

This I would presume would start the PATH search in "current directory".

HTH /Michael

 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.