We have a common compiled code library that is only accessible to a number of advanced developers within our company. We build releases for it periodically, releasing a ‘release’ version for our dev, test environments and a debug release for developers to use.
Oddly, when I build the Debug release, references to the path of my project on my PC show up when another developer tries to use the Debug version of the DLL on their PC. I haven’t worked extensively with compiling these DLLs, but I should be able to build a Debug release and give it to other developers to use within their projects, correct? Or is that not how it works?
When you build a debug version, you’re also building the .pdb, which contains the symbols required for debugging. This is going to include the file paths, line numbers, etc, and be based on the system where this library is built. That’s why they see these paths.
That being said, this won’t hurt anything – they can use the assemblies to debug, but won’t be able to see the code itself when something happens, as they won’t have the projects.