views:

850

answers:

2

In prior versions of visual studio one could specify paths for DLLs when debugging an application. I do not see a way to do this is version (2008). Is this due to the move toward deployment of apps with all DLLs, etc in the application's directory(ies)?

Am I missing something, or is there no way to do this?

EDIT:

It was in VC6 I think it was Tools - Options - Directories - executable files

Perhaps now this was not what I thought it was - this may be the same as what I have found in 2008.

basically I am looking for a way to "append" to the PATH env var - just for running the exe project open in visual studio. (without actually editing the path env variable)

The workaround is for me to copy all the dependencies to the working directory. That will work - it just involves some changes to other projects - and gathering 3rd party stuff. (this was a huge migration from VC6)

A: 

Tools -> Options -> project and solutions , where you can specify all the search path for your project.

J.W.
Yeah - i saw that one before. Looked promising the comment is that it is for exes to look for when BUILDING a project - not for looking for DLLs when debugging. I'm guessing
Tim
There are a couple of options in the drop down, one is called "executable file".This is what it says:Executable files.Path to use when searching for executable files while building a VC++ project. Corresponds to environment variable PATH.
J.W.
+1  A: 

It doens't work that way anymore (since VS 6.0), today once a DLL is loaded by the process the dll gets a notification and search for the dll debug symbols.
First it looks inside the dll (dll can keep the path for the debug symbols) if not it search the symbol path (Tool->Options->Debugging->Symbols) then it looks inside the window directory.

It try to load the debug symbol only if needed (To resolve a breakpoint for example) or if you manually ask the symbols to be loaded (In the case if the symbols were not found it will prompt you for them).

You can see where the debugger have tried to look for the symbols by openning the modules pane (Debug->Window-> Modules) right clicking on the module and selecting show debug information (It don't have VS here so it might be called by a different name).

Thanks God(s) that we no longer need to configure the path for each dll.

Shay Erlichmen