Why Arent Breakpoints Working In Web Application Project

My company gave me a web application project and I went to debug it and set some breakpoints and they don开发者_高级运维t fire. I am using Response.Write all over the place to debug. Anyone know what maybe going on?

I am running the application off my localhost I was pushing F5, but since the breakpoints dont hit by making changes and adding Response.Write statements and clicking save then refreshing my browser I get the changes for whatever reason.

Hovering over the breakpoint it says "The breakpoint will not currently be hit the source code differs from the original version"

Another tidbit is I created a new web application project and created a breakpoint and it works, its only specific to this application it seems like, but dont know what it could be?

Hovering over the breakpoint it says "The breakpoint will not currently be hit the source code differs from the original version"

Try this:

• Close Visual Studio and make sure any instances of ASP.NET development server are closed as well
• Delete everything from "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files" (where v4.0.30319 is the version of your .NET Framework)

Definitely need more info, but I would check that your are building with debugging symbols to cover the dumb stuff.

Okay, after reading the comments posted on your question I was making the following assumptions.

• You are running using the built in VS development server
• You are compiling in debug mode
• You've set debugging true in your web.config

I've seen this problem before and for me it's been resolved by restarting Visual Studio.

Assuming that you are running on IIS on the same machine that you have visual studio installed:

• Have you attached to the application pool process
• Is you code the same as what is deploy? (Is the latest version deployed)
• Are you logged in as administrator?
• Are you running visual studio as administrator?

Just to make sure, you are running in debug mode?

I ran into this problem a while ago as well, instead of using response.write, you could try outputting the data to a label control's text value instead to see the values of your code.

It's a bit of a sloppy work around, but I couldn't figure out why that one particular project I was working on didn't let me debug it.

This problem is, for me, mostly caused by a mismatch of the loaded dll files (symbols) by webserver, and those that the project are pointing to when you try to breakpoint. It's different files. I have located different causes. One could be a simple hang-up by webdev instans (force shutdown. But also that there occur some kind of mismatch if you got different compilation methods between project within same solution as the web project.

This desc may not be your exact problem, but perhaps it will lead you into right direction. I find this often being a dirty unlogic error that just are irritating (but also completely fixable without data loss or reconfiguring, when u understand the trick).

I had the same problem, and it turned out only Internet Explorer works with debugging and breakpoints. To avoid having IE as my default browser, I changed the launch settings in the .Web project to run IE with the path as command line parameters.