Breakpoints not working, what could be the reason?

Question

Command line

Good day everyone. There is MS VS 2015 Ent. There is a C++/CLI project with VS 2013 support mode. In the C++/CLI code I put a breakpoint (breakpoint) - the compiler completely ignores it. Debugging with IDE tools and tools is required. I rechecked the settings of the solution, project and IDE in terms of debugging by 10 times, tried a bunch of methods from posts on StackOverFlow - at least henna. What could be the reason for ignoring breakpoints?

Answer 1

In C++/CLI projects, downgrading the target framework (Toolset) in the project settings crashes the compiler, linker, and debugger settings. It is practically impossible to correct the settings by hand - and this is due to the fact that some of the project properties are hidden, including the CLR platform setting (.Net Framework version), the target platform setting (Windows 8.1 by default), which affects the "pulling up" of all tools listed above. Installing Microsoft Build Tools 2013 won't help either. The only solution found so far is to install MS VS 2013 and work on the project in it.

Answer 2

Try to rebuild the project

Answer 3

Go to modules and check if symbols are connected.
Debugger->Windows->Modules (I'm writing from memory, MB is not there)
The bottom line: there is a list of all dlls marked with symbols loaded / not found and the ability to see the details.
If connected, then they could connect from the wrong place.
Therefore, I recommend deleting all symbol files from the project folder.
Then rebuild the project.
I don't know about the CLI, but C++ might still have a problem with rebase.
If the exe / dll was not loaded at its usual Base Address, then the symbols may not work either,
this is solved by adding a forcibly different Default Base Address in the project settings.
For exe it will not load at the usual Base Address, this is a rarity, but for dll it is a common thing.
Also, I had a problem with debugging a regular C ++ dll precisely because I chose the 2010 studio toolset instead of the 2015 studio toolset. Breakpoints did not work because of this.
In this case, you can debug under 2015, and build Release under the toolset you need.

Answer 4

But try removing all breakpoints. I had the same problem and it was solved by deleting it.