VS 2013 breakpoint will not currently hit. no characters were loaded for this document

VS2013, windows 8.1, windows phone 8 C # app Breakpoints that do not work and I got a breakpoint will not be deleted at this time. no characters were loaded for this document error, what do I need to do?

Image

+6
source share
6 answers

You must build your project, if it is built, make sure that you join the right process! If you are sure that all these 2 are in order, clear the solution and restore again.

+1
source

I struggled to fix it. Finally, this is what I have done for me.

Choose Debug → Preferences → Debug → General

Mark Enable .NET Framework Source Stepping.

(This may be all you need to do, but if you are like me, you also need to do what is indicated below. The solution below will also fix errors when your project loads old builds /.pdb files, despite restoration and cleaning.)

Choose Tools → Options → Projects and Solutions → Build and Run ,

Untick Only create run projects and run dependencies ,

Choose Always build from the On drop-down menu when the project is out of date .

+7
source

This usually means that any of your assemblies has changed, but has not been rebuilt, or rather, the Debug-Information-File (PDB) is not the last. Therefore, the debugger does not know the correct source code and therefore cannot enter it. Restore assemblies and attach them to the correct process.

You can also take into account that assemblies created for .NET 3.5 down cannot be processed together with assemblies for .NET 4.0 up, you cannot debug both types at the same time.

EDIT. To make sure that I mentioned before checking the type of assembly for which debugging information is generated. When attaching an assembly to an existing process, click the "attach to" selection button. There you can choose the correct type, if you do not do it automatically.

+3
source

For me, this helped kill IIS (if used (ASP.Net)) and close and restart Visual Studio. It may sound very stupid, but sometimes it helps to just reboot.

0
source

My solution to this problem when I ran into this was to disable the Team Foundation Server (TMS) - as I use it - and republish the website.

0
source

For me, even the latest code changes will also not be implemented in the application. So I made a small compilation error in the code where the breakpoints are, then try to run the solution after a clean build. He gets into an error, and then I correct the error and start it again, now even it gets to breakpoints.

0
source

Source: https://habr.com/ru/post/975523/


All Articles