When we do a Release build we generate PDB files which we keep in case we need to analyse crash dumps sent by users. The PDB files are kept private and are not released to users.
By doing this, the Visual Studio linker inserts the full path to each PDB file into the respective binaries. As the PDB files are kept in our source area, this reveals the full path to our source code.
We dislike this because there's nothing to gain from making that information public and it may reveal things which haven't been made public. (e.g. If we give someone a test DLL built from a branch directory named after something we haven't announced yet. It also seems silly to tell people where you keep your private source code and, if it's built below a user profile, the account name used to build it.)
VS2008 had an undocumented linker argument, /pdbpath:none , but this now results in an error in VS2010.
Is there a new way of doing this or something I have overlooked?
The only alternative I've found is to output the PDB files to a generic path (e.g. C:\temp) and then move them to where you really want them as a post-build step. That's obviously quite inefficient, though.
Thanks for reading!