The breakpoint is not currently affected, why not?

Question

Sometimes I get a message that the breakpoint will not be deleted and no characters will be loaded.

The red icon in vs .net changes color, and the debug mode just doesn't work.

what is the reason for this?

Answer 1

1. only for code management - there is a good answer to this problem on the following site: http://geekswithblogs.net/dbutscher/archive/2007/06/26/113472.aspx
2. for native + managed code - in the solution for launching properties-> the Debug tab, make sure that the checkbox "enable debugging of unmanaged code" is checked

Answer 2

Make each bullet in the link below ONCE, but repeat my steps below with each one you try.

http://web.archive.org/web/20140212130754/http://carnotaurus.philipcarney.com/post/4130422114/visual-studio-debugging-issue-with-files-of-the-same

1.) Stop debugging (click the red square icon) in Visual Studio
2.) Pure solution
3.) Build a solution
4.) [INSERT THE BULLET INSTRUCTION HERE]
5.) Tools> Attach to the process (or start with debugging)
6.) Run the program you are joining and run it so that your code gets hit

6 explained:

If you connect to nunit.exe, open NUnit and run the test to reach the breakpoint.

If you connect to w3wp.exe (IIS site), open your site in a browser and go to the page that reaches your breakpoint.

Answer 3

After trying a few suggested fixes for this, I did the following to make it work.

• Right-click my project in Solution Explorer and select Properties.
• I went to the "Web" section and made sure that the "Start action" parameter was set to "Current page".

I worked 3 1/2 hours on this ... I'm going to drink now.

Answer 4

This can happen if the characters do not differ from the assembly (remote debugging) or when there is no “direct path”, so the hasent assembly has been loaded, but can be loaded using reflection and loading the required assembly at runtime.

Answer 5

This can also happen if the debugger is not associated with the process for any reason. If so, you can always go to Debug - Attach to Process ... and select the correct process. Your breakpoints should return to normal after VS determines that it can hit them.

Answer 6

I solved this problem by selecting Automatically: native code for the Attach to field in the " Attach to process form"

Answer 7

What does it say when you hover over a disabled breakpoint? This usually tells you about the problem. My favorite old "source code is out of date", especially when I'm debugging a DLL. Another favorite is when the file you are looking at is not the one you are debugging (copy in another folder?). If this is the case when you can intercept the calling procedure, but not the called one, interfering with the called party will force VS to open the "correct" source file, and you can set breakpoints. Embarrassingly, I usually swear by VS at the moment, this seems to help.

Answer 8

I don't like playing with knives, but the only thing that worked for me was editing the .csproj file itself. So, upload the project file, edit it by cutting and pasting the three asp.net files so that they are 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 - In addition, I provide a list of other suggested ones solutions that do not work for me. Hope this helps.

Answer 9

I had the same problem. Usually I know if the build versions are different from each other, and something does not match. I cleaned my project, rebuilt it, and then deployed, and everything was restored.