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