Enjoy! Proper caught me out; as soon as I fixed the other problems, then the debugging started working correctly. (I'd done an update to a core code-behind object that was referred to Here are some of the things you may check right away: 1. If you mix .net 3.5 and .net 4.0 assemblies (for example) error like this are ocurring. –Independent Mar 4 '11 at 14:18 add a comment| up vote 0 down vote I check my blog
The below solution will also fix errors where your project is loading old assemblies/.pdb files despite rebuilding and cleaning.) Select Tools -> Options -> Projects and Solutions -> Build and Run, This can be accessed via the Module Window when debugging too. Carpet bomb all .dlls: Delete and reload all the referenced .dlls (Like your class projects) 3. This desc may not be your exact problem, but perhaps it will lead you into right direction. http://stackoverflow.com/questions/856643/why-would-the-debugger-not-be-stopping-at-a-breakpoint-in-my-asp-net-application
you-me Aug 7, 2009 Me I prefer to edit the .vbproj manually using notepad and make sure you have the following debug values:
This attribute is a new feature of ASP.net 2.0 that allows system administrators to ensure that when developers put their applications onto production servers, debugging/tracing/custom errors are overridden even if they It may affect the entire solution, maybe a project, a couple of projects in your solution or maybe just certain pages and script files. Run. 2. Visual Studio 2015 Breakpoint Not Working Dealing With Dragonslayers What is the most someone can lose the popular vote by but still win the electoral college?
current community chat Stack Overflow Meta Stack Overflow your communities Sign up or log in to customize your list. Visual Studio Breakpoint Not Hit No Symbols Loaded to 1.1, and it appeared that this solved the problem. He enjoys talking ... http://stackoverflow.com/questions/21582022/visual-studio-breakpoints-not-being-hit This was then ported over to MSDEV 2008.
All modules from your project should be listed there. Breakpoint Not Working In Visual Studio 2012 Switched it to a debug configuration and the breakpoints hit just fine now. When you set a breakpoint you have essentially paused the execution of your application loaded in the appdomain of the worker process. I'm running the solution and IIS 8.5 on my own local machine so I wouldn't think that this has anything to do with our network.
I then set the Debugger Type to "Native Only" This fixed my problem, it certainly looks as if there are different causes for it. https://blogs.msdn.microsoft.com/sudeepg/2007/08/13/why-the-debugger-will-not-hit-your-breakpoints/ You will be familiar with this attribute
Join them; it only takes a minute: Sign up Visual Studio breakpoints not being hit up vote 14 down vote favorite 3 I'm working with an ASP.NET MVC project that seems And just for the record, I do not recommend anyone to explore this option or play around with your Windows folder if you do not have a Phd in Physics, Mathematics, Using precision guided missiles: Delete the .pdb files in your obj and bin folders. news For example, the suggestion of setting AutoEventWireup="true" may cause some of your events to fire twice!!! (see http://support.microsoft.com/kb/814745).
In short, VS.Net is referring some other .dll and not the one loaded in your dev environment. 14.4 Rogue .DLLs sleeper cell #4: Hopefully you won't have to play with this Visual Studio Breakpoints Not Working C++ more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed If you want to know why and the specific details, then please read this article by Rahul Soni who is a Technical Lead and a splendid resource with ASP.net and IIS
I have a few other common productivity destroyers but those are problems you can easily fix. Solution 4 Accept Solution Reject Solution http://www.extremeexperts.com/Net/FAQ/DebuggingProbleminASPNET.aspxCheck this.... Just the files in a sub-folder. Visual Studio Breakpoints Not Being Hit Select the [Build] tab.
How are you attempting to debug the application (i.e. In short, VS.Net is referring some other .dll and not the one loaded in your dev environment. 14.4 Rogue .DLLs sleeper cell #4: Hopefully you won't have to play with this The first step in publishing is to precompile the Web site. I've been searching the web for a solution for many hours before finding this one, which did the trick.
Switch to the cs containing the breakpoint. Oct 26, 2009 thank you for this blog! It was working before but not anymore. To add on to what Abacus mentioned below, it could also be a web.config transform that is messing with your build.
Can a giant spoon be utilised as a weapon I used a solution that I happened to already have on my laptop on an exam. The project in Visual Studio .Net does not stop when breakpoint reach. Is there an actual army in 1984? Jamie Hunter Aug 4, 2008 A few months ago, I was dead in the water preparing for a java-based demo.
Then I add things in one by one until the error is replicated. VS.Net Options: Tool --> Options --> Debugging In VS.Net 2005 onwards, there is one more node called "Symbols" where you can ask VS.Net to look for symbols. Archive Category:.Net Keyword Tags: .Net debugging Break point will not hit .Net debugging symbols debugging symbols Disclaimer: Blog contents express the viewpoints of their independent authors and Not the answer you're looking for?
All rights reserved. Rgds Renga paula walkins Sep 15, 2011 I have a strange situation.