Home Library Learn Downloads Support Community
Sign in | United States - English | |
5 out of 27 rated this helpful - Rate this topic

Debug Source Files, Common Properties, Solution Property Pages Dialog Box

Visual Studio 2005

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

Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
Can't find common properties
Hi, $0$0 $0 $0I can't find Common Properties in the solution explorer property for VS 2010. would you please  help ?$0 $0$0 $0 $0$0 $0 $0Regards$0 $0$0 $0 $0Bunthoeun$0 $02011-07-11$0
History
There is no source code available for the current location

Hi,

When i added to Calender extender to this my page.i am getting following exception along with "There is no source code available for the current location" one message box will popup with two options 1)OK 2) Show disaassembly. I am new to ajax please help me.

Thanks,
Yashwanth

The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>).

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>).

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:

[HttpException (0x80004005): The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>).]
   System.Web.UI.ControlCollection.Add(Control child) +8680855
   AjaxControlToolkit.ScriptObjectBuilder.RegisterCssReferences(Control control) in d:\hg\act\Server\AjaxControlToolkit\ExtenderBase\ScriptObjectBuilder.cs:323
   AjaxControlToolkit.ExtenderControlBase.OnLoad(EventArgs e) in d:\hg\act\Server\AjaxControlToolkit\ExtenderBase\ExtenderControlBase.cs:305
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Control.LoadRecursive() +141
   System.Web.UI.Control.LoadRecursive() +141
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
History
Another way to solve this
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.
History
Perfect... this is just what I was looking for!

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.

History
Delete files from Debug and Release directory
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.
History
Locating source file is such a pain
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...
History
Page does not describe real situation.
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.
History
Advertisement