Breakpoint not hit

organicglenn · October 12th, 2004, 12:57 AM

I use Visual Studio 2002.
On a couple of pages, but not everywhere, when I run the app, the breakpoints show question marks inside of them and the rollover says, "The breakpoint will not currently be hit. No symbols have been loaded for the document."

Why would this happen? I tried deleting all the dlls and pdb files and doing Rebuild All, but that didn't fix it.

englere · October 12th, 2004, 09:20 PM

You need to give us specific examples. Maybe you put breakpoints in a file that isn't used - there are definitely some of these!

Or maybe you had the right file, but the wrong folder.

Or maybe you put breakpoints on a user control that gets compiled dynamically.

Eric

organicglenn · October 13th, 2004, 01:36 AM

I don't understand the first 2 scenarios you mentioned, but it's not a user control. I can't put breakpoints anywhere in the files, and couldn't post the entire files, so...

The problem with the breakpoints is in two code-behinds in the "ThePhile/WebModules/modulename folder. These are files in the Modulename.Web namespace, not ModuleName.Business or ModuleName.Data:
http://localhost/ThePhile/modulename/MyAccount.aspx
http://localhost/ThePhile/modulename/Default.aspx

So the problem is confined to one folder. The project has 'enable ASP.NET debugging' checked, and I can successfully set breakpoint in the other files in the project that are not within this folder.

organicglenn · October 19th, 2004, 11:09 PM

I'm still having this problem. Here's what I know:
If I change the names of the two aspxs(myaccount.aspx and default.aspx) I can set breakpoints successfully. If I change them back, the problem reappears.

If I remove the files from my project, and then add two new files with the same names, and paste in the original content, the problem persists. All around these tests I delete all the dlls and pdb files from the project directory, VsWebCache, and some other cached folder whose name I forget.

i thought maybe it was a name conflict, and maybe it is, but I noticed that my default.aspx is actually the 3rd default.aspx in the main web project, after the root default.aspx and WebModules/Accounts/Admin/default.aspx, and there's no problem debugging the first two...so why a problem with the 3rd.

I noticed this in webproj.csproj. All the 'dependentupon' are the same, but that seems correct, though counterintuitive. Help is appreciated.

Code:

        <Files>
            <Include>
                <File
                    RelPath = "Default.aspx.cs"
                    DependentUpon = "Default.aspx"
                    SubType = "ASPXCodeBehind"
                    BuildAction = "Compile"
                />
                <File
                    RelPath = "WebModules\Accounts\Admin\Default.aspx.cs"
                    DependentUpon = "Default.aspx"
                    SubType = "ASPXCodeBehind"
                    BuildAction = "Compile"
                />

                <File
                    RelPath = "WebModules\Pools\Default.aspx.cs"
                    DependentUpon = "Default.aspx"
                    SubType = "ASPXCodeBehind"
                    BuildAction = "Compile"
                />
.
.
.

englere · October 20th, 2004, 10:15 PM

I'm not having this problem, but one other user said there's a problem having more than 1 page with the same name.

It seems smart to rename the pages so they have unique names, especially if it fixes your problem. Why don't you want to do this?

Eric

organicglenn · October 22nd, 2004, 02:21 AM

Because I've been stubborn. Default seemed like a useful name in several places, but it's the most realistic thing to do at this point to change it.
Thanks

SteveC33603 · December 16th, 2004, 03:43 PM

You are most likely getting this error because your build mode is set for release. Under build select build options and set the build to debug then re-build the project. This should fix this error.

titeoe · January 5th, 2005, 07:46 AM

hello I had the same problem and finally i fixed it.

there are 4 points to look for :

1/uninstall and reinstall your aspnet process
aspnet_regiis -u to uninstall
aspnet_regiis -1 to reinstall

2/check if you're not in realease mode for all projetcs in your solution

3/in the project properties options check if "enable ASP.NET debugging" is set to true

4/ and the very last one not found in previous posts
in the project properties options : "common properties/general/startup object"
it must be set to "not set"

if you set it to your startup page it wont work and aspnet won't be abble to load all debugging informations in the pdb file.

comment : this works for the C# projects, didn't checked with other languages.

I hope you will be sucessfull in debugging your projects.

:))))
--------------------------------
From: titeoe Mr

SudhaMallenahalli · January 31st, 2005, 12:53 PM

Hi:
I am having the same problem with vb.net 2002. "The breakpoint will not currently be hit. No symbols have been loaded for the document." I have 2 projects in my solution: #2 references the dll of #1. When I set a break point in #1, it does not stop at the break point. I have rebuilt the solution and tried. My Configuration is set to Debug.

What else could I check for?

Thanks in advance.
Sudha

englere · February 2nd, 2005, 01:29 AM

Can you set a breakpoint in a simple web forms project you create yourself?

Eric