.NET 2003 link-library dependency-checking bug

[James Edwards]

There seems to be a bug in the link-library dependency checking in VS.NET 2003.
Under the Configuration->Linker->General->Additional Library Directories
property,
if you specify a directory name such as "$(SolutionDir)\..\lib", it will
link properly, but when you try to run in the IDE will complain that the
"project configuration is out of date." It turns out that $(SolutionDir)
already contains a trailing '\', so that changing the "Additional Library
Directories" to $(SolutionDir)..\lib will remove the repeated '\' and
suddenly the IDE stops complaining the project is out of date. The
dependency checker apparently gets confused by multiple repeated backslashes,
which it should not since the file system and linker handles it fine.

[Ronald Laeremans [MSFT]]

Hi James,

This is a known issue with VS 2003. You might want to report it on
http://lab.msdn.microsoft.com/productfeedback/ to make sure someone from our
team will try it on Whidbey and to allow other customers to vote on this if
they consider it important.

Thanks!

Ronald Laeremans
Visual C++ team

"James Edwards" <Ja**********@discussions.microsoft.com> wrote in message
news:22**********************************@microsof t.com...

There seems to be a bug in the link-library dependency checking in VS.NET
2003.
Under the Configuration->Linker->General->Additional Library Directories
property,
if you specify a directory name such as "$(SolutionDir)\..\lib", it will
link properly, but when you try to run in the IDE will complain that the
"project configuration is out of date." It turns out that $(SolutionDir)
already contains a trailing '\', so that changing the "Additional Library
Directories" to $(SolutionDir)..\lib will remove the repeated '\' and
suddenly the IDE stops complaining the project is out of date. The
dependency checker apparently gets confused by multiple repeated
backslashes,
which it should not since the file system and linker handles it fine.