Debugging and linking conflicts with VC50.PDB
I solved my own problem, sort of. I created an additional configuration
for the project, based on the Debug configuration. This configuration
must unfortunately recompile everything, but afterwards everyone can
debug using the output files rather than the .PDBs that I need to
rewrite when I compile.
Quote:
> -----Original Message-----
> From: Brian Moore
> Posted At: Wednesday, January 14, 1998 1:20 PM
> Posted To: de{*filter*}
> Conversation: Debugging and linking conflicts with VC50.PDB
> Subject: Debugging and linking conflicts with VC50.PDB
> We have several programmers working on individual components for a
> project with a container. When one of us is debugging his component
> using the container, the other can't link the container because the
> VC50.PDB file is locked. We were able to get around this problem for
> the container's .PDB file by releasing it along with the .EXE into a
> path that all of us have in our executable path. Unfortunately, there
> is a VC50.PDB for all C++ projects. How can we get around this as
> well? A speedy tip may prevent {*filter*} from breaking out among the
> masses here...
