Click to Rate and Give Feedback
MSDN
MSDN Library
Visual Studio 2005
Visual Studio
 Debug Source Files, Common Properti...
This page is specific to
Microsoft Visual Studio 2005/.NET Framework 2.0

Other versions are also available for the following:
Visual Studio Debugger
Debug Source Files, Common Properties, Solution Property Pages Dialog Box

This property page specifies where the debugger will look for source files when debugging the solution.

To access the Debug Source Files property page, right-click on your Solution in Solution Explorer and select Properties from the shortcut menu. Expand the Common Properties folder, and click the Debug Source Files page.

Directories containing source code

Contains a list of directories in which the debugger searches for source files when debugging the solution.

Do not look for these source files

Enter the names of any files that you do not want the debugger to read. If the debugger finds one of these files in one of the directories specified above, it will ignore it. If the Find Source dialog box comes up while you are debugging and , you click Cancel, the file you were searching for gets added to this list so that the debugger will not continue searching for that file.

See Also

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Page does not describe real situation.      joeller   |   Edit   |   Show History
This page is false in so many ways. There is no solution in the solution explorer only a project. clicking properties on the short cut menu does not bring up a tree with folders to be expanded. The source code for debuggin was available all night until suddenly at about 2:00 AM it decided that there is no source code at that location. Naturally this occured as I was on the verge of completing that application.
Tags What's this?: Add a tag
Flag as ContentBug
Locating source file is such a pain      kennethxu ... lucmaxius   |   Edit   |   Show History
I'm using a debug version of lib that was compiled by somebody else from I: drive. I have the source code put in D: drive and hoping the VS to find them after I specified the debug source. But with not luck, come to this page just to find out such a useless page. It was so much eaiser to do this in eclipse with Java. Sigh...
Tags What's this?: Add a tag
Flag as ContentBug
Delete files from Debug and Release directory      lucmaxius   |   Edit   |   Show History
To escape the "No source available at current location" I have removed the reference to the "unlocated" dll, deleted the dll from debug and release directory, and then added the reference to the dll project. It worked and now I could debug code in dll.
Tags What's this?: Add a tag
Flag as ContentBug
Perfect... this is just what I was looking for!      JShortOC   |   Edit   |   Show History

Thank you, we were looking for this solution for some time now. This was extremely helpful. This solution works just as described. You can also add a root directory instead of the actual directory and it still finds the files.

Tags What's this?: pdb (x) Add a tag
Flag as ContentBug
Another way to solve this      AbhayBarhanpurkar   |   Edit   |   Show History
I was having similar problem while debugging the unmanaged code from managed one. Typically, you would get this error because of the rpc*.dll function involved in the process for which you do not have the source code. I opened the required unmanaged source file, set the breakpoint and pressed go to reach the required breakpoint in my code.

Alternatively, while you are in dis-assmbly, you can open the call stack and press Step-Into untill you see your dll function loaded in the stack.
Tags What's this?: Add a tag
Flag as ContentBug
Processing
© 2010 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker