The reason for the current VS.NET breakpoint will not be removed 'warning?

Trying to debug the action method of the controllers and when I attach to the process the debug icon crashes and says "the current breakpoint will not be removed"

But I do response.write

at this point, and when the page renders it, it outputs the test text.

So this section is actually running, why isn't debug mode working?

+2


source to share


6 answers


The source code may differ from the version of the corresponding process you are linking to. Your other process can also be created in release mode i.e. No debug info available.



+6


source


There are several reasons why you might see this message:



  • You are connected to the wrong process.
  • You are connected to the correct process, but the AppDomain has not loaded the assembly yet
  • You are tied to the correct process, but you forgot to build, so the source code and PDB file are out of sync.
+4


source


I noticed this happens when using reflection and dynamically loading DLL projects. If the code isn't specifically referenced (i.e. you're using an animal interface, but dynamically loading animal implementations like cat / dog), it will say it won't hit a breakpoint, but it actually does.

+1


source


I don't like playing with knives, but the only thing that worked for me was editing the .csproj file itself. So, unload the project file, edit it by slicing and pasting the three asp.net files so they go together in the ItemGroup. However, sometimes you need to go further as described here: http://carnotaurus.tumblr.com/post/4130422114/visual-studio-debugging-issue-with-files-of-the-same - Also, I provide a list of other suggested solutions that don't work for me. Hope this helps.

0


source


Another reason is that you quickly join the process.

For example, when I connect to Excel to debug a VSTO add-in (I am using Add-In Express), if I create, then Start> Run> Excel, then quickly press Ctrl+ Alt+ Pto attach to the process, then press E, to highlight Excel and click EnterI see this before Excel loaded: enter image description hereNo breakpoints as a result. ...

However, if I give Excel a couple of seconds to load and then press Ctrl+ Alt+ P, notice that the title shows: enter image description here

This will remove breakpoints ...

0


source


It also informs me that your source code is different from version, but this is not correct. I am building the whole solution and then attaching to the process, but still it says that the breakpoints will not be affected because the original code is different. Could it be a mistake?

0


source







All Articles