Hi,

I had gotten a whole new application off of another computer and when I run the project, it runs fine and also breaks at the specified break points. But any new code that I put in, at the break point it doesnt break. When I hoover over the red circle it says " The breakpoint will not currently be hit. No symbol have been loaded for this document."

I was reading the other threads similar to this problem but did not solve the problem

Are there any suggestions?

Thanks,
Deepti.

Short answer:

Using Visual Studio 2005

In the Solution Explorer, Right click on the project.

Select the tab Compile

Push the button Advanced Compile Options

Uncheck the box enable optimizations.

Hope this helps someone. Drop me a line if it does.

Phil

Looks like the assembly you are trying to debug is in GAC. Uninstall the assembly from GAC and try to debug. Please me know if this is working.

Vijay

Short answer:

Using Visual Studio 2005

In the Solution Explorer, Right click on the project.

Select the tab Compile

Push the button Advanced Compile Options

Uncheck the box enable optimizations.

Hope this helps someone. Drop me a line if it does.

Phil

I don't know how common this variation of the story is, but I encountered the "breakpoints will not be hit" issue yesterday in my C# ASP.NET web app. Ultimately I found that the site was not generating its pdb files, but it would still compile and run in debug mode.

Without the pdb's, no breakpoints. So, what was preventing the pdb creation? I'm not sure what the exact reason was, but I was able to narrow it down to being related to two .htm documents I had added to my project. One of them was specified as the startup document. I've never had an issue adding .htm docs to an ASP.NET project before, but apparently the compiler did not like something about these files even though it didn't throw any errors or warnings. Maybe I had some invalid markup according to XHTML standards or something. Not sure...

...but I'd recommend as an alternative solution approach to anyone wrestling with this issue...look at the recent file changes/additions to the project. Try re-tracing your steps by removing those changes/additions 1 at a time and see if it will compile and generate symbols.

One other clue was that my intellisense on the specific namespace of System.Web.UI was unavailable even though the namespace was referenced. Again, no compile errors occurred, but obviously there was something amiss. Hope that helps somebody avoid major system config approaches.

Ccrookston,

Sorry for your troubles. I wonder if you've figured out a solution for this yet. Would it be possible for you to convert the web site to a web application project?Have you tried that? If you create a new web application project and try to debug it does that work?

What I meant about the intellisense was that normally if you start typing out a namespace or a typename qualified by the full namespace intellisense will do its usual thing and display a drop down of matching child namespaces or types. When I was having this problem with my web app, the System.Web.UI namespace would not respond this way. I would get no intellisense dropdown for that namespace. Other namespaces worked, but not that one. Weirdly though I did not get any compile errors or warnings and types contained by that namespace continued to function. It was a clue though, that there was something really off in the project. Again, for me there were two htm files that VS2005 was quietly hating. Not sure why. When I removed them, the problem went away.

-Very Bad Horse

Bad Horse,

No, for this project I have not figured out a solution. When I start a new website or web application, I can debug just fine. But with this one I can not get it to work. I converted this project from 1.1 to 2.0 mid stream, and I think there is something wrong somewhere, (obvioiusly) but I have no idea what. But I also can't spend any more time trying to figure it out, and it's too big a project to simply start over and rebuild entirely in 2.0.

- Ccrookston

I don't know what to say, when I get the properties for a solution in VS2005, I get a window with the following tabs, Application, Compile, Debug, References, Resources, Settings, Signing, Security, and Publish. This is not in the Properties frame, but in the same frame as your code.

Phil

I don't know about the specifics of this problem, but the same core problem must be resolved, you must find out why the PDB file is not being created properly. That is where the break points are stored.

With my problem, the code was "optimized", which meant no debugbreakpoints were created. Apparently there are other ways yet to be identify to kill an obviously valuable feature.

Phil

>>I don't know what to say, when I get the properties for a solution in VS2005, I get a window with the following tabs, Application, Compile, Debug, References, Resources, Settings, Signing, Security, and Publish. This is not in the Properties frame, but in the same frame as your code.<<

I don't. It seems to be because this is a "website" project. If, from the File menue in VS2005, I select "Create New Project" then I see the properties you describe. But if I select "Create New Webiste" then I don't.

Well I had the problem whilst i was developing a asp.net application all of a sudden my breakpoints are not being hit, well all this does is just bring about fustration for a developer on a tight schedule, i managed to solve the problem on my vista machine runinng vs2005, To me the problem seems to be related to internet explorer setting and when i checked the asp.net cache the pdb files were not being generated.first i unchecked Disable Script Debugging (Internet Explorer) in the Advanced tabgod knows how that got checked. then second added http://localhost to trusted sites in the security settings this solved the problemo on my box hope it works for you guys.

Hi,

I too getting the same problem. I don't know what the MS peoples doing and what the moderators doing. Might be, MS Peoples forgot this option. They limit to work with only one project. MS applications sink's day by day.

I have seen this problem, when the program being executed is in factNOT the program shown in the debugger.

Actually fair enough.

If you want to debug a program, that is started from outside you must catch the process from the menu "Tools - attach to process".

As soon as the debugger attaces to the process, the red circles around the breakpoints disapear.

To have enough time to catchthe processwhile it is running, you might want toput a delay in the code before your breakpoint.

This can be made by a loop or by a thread.sleep(30000) giving you 30 seconds to mouse around the debugger.

But be shure that it is the debug builded version of your program that is actually started. You can simply copy it to the right position if needed.

regards

Had the same problem and it solved itself (sic)like this:

1. Tried to put breakpoint in my website and that worked fine to debug until I tried to debug from a pc with newly installed vista and Visual Studio. Impossible to debug, tried to put a breakpoint in the page_load of the default page and the debugger would not pick up the breakpoint when run. Went back to the old workstation and the same breakpoint worked fine. Booted all machines (server and workstations), old works, new does n't.

2. Icreated a new VB projectwith the newworkstation and tested if that would debug. Worked fine to debug.

3. I started a new web site, put some code in the page_load and a breakpoint. Worked fine to debug.

4. I checked the web site created in 3if there was any "visual studio project" files created but found nothing.

5. Opened my old web site again and now then running debug it worked fine to debug.

So a few new ms greyed hairs later it solved "itself" ?!?!

Checking 'Emit debug information' in the 'Publish Web Site' dialog did the trick for me

Had the same problem yesterday, but it seemed to have a very odd cause; localhost (as in http://localhost:port) was being resolved to an IPv6 address of "::1" - trying to "ping localhost" worked, but shows the address as ::1. Changing the localhost address in hosts to 127.0.0.1 fixed it.
Dunno what caused my hosts file to be updated (it certainly used to have 127.0.0.1) but I've posted more info at http://skotl.blogspot.com/2009/04/breakpoint-will-not-currently-be-hit-no.html

Cheers
Scott