Symbols are created, but debugging never stops at a break point

Question

How to make my control points work?

I get this message when starting a C # console application in debug mode:

Currently, the breakpoint will not be deleted. No characters have been uploaded for this document.

Here are other specifications related to this issue:

Microsoft Visual Studio Professional 2015 update version 14.0.25123.00 2 Microsoft.NET Framework version 4.6.01055

Installed Version: Professional

ASP.NET and Web Tools 2015.1 (Beta) 14.1.11106.0 ASP.NET and Web Tools 2015.1 (Beta8)

ASP.NET 2012.2 Web Platforms and Tools 4.1.41102.0 For more information, visit http://go.microsoft.com/fwlink/?LinkID=309563

ASP.NET 2013 Web Platforms and Tools 5.2.40314.0 For more information, visit http://www.asp.net/

Code Alignment 12.1 Code Alignment helps you present your code beautifully, improving clarity and readability.

CodeMaid 10.1.93 CodeMaid is an open source Visual Studio extension for cleaning and simplifying our C #, C ++, F #, VB, PHP, PowerShell, R, JSON, XAML, XML, ASP, HTML, CSS, LESS , SCSS, JavaScript and TypeScript coding.

Common Azure Tools 1.7 Provides common services for using Azure Mobile Services and Microsoft Azure Tools.

ConfigurationTransform 1.3 Automatic conversion of app.config during the build process. Once the conversion is established, it will work on another build machine without expansion.

GitHub.VisualStudio 1.0 The Visual Studio extension that brings GitHub Flow to Visual Studio.

JavaScript Language 2.0 2.0 Language Language Service

JavaScript Project System 2.0 JavaScript Project System

JetBrains ReSharper Ultimate 10.0.2 Build 104.0.20151218.120627 JetBrains ReSharper Ultimate Kit for Microsoft Visual Studio. For more information about ReSharper Ultimate, visit http://www.jetbrains.com/resharper . Copyright © 2016 JetBrains, Inc.

Microsoft Azure Mobile Services Tools 1.4 Microsoft Azure Mobile Services Tools

Node.js Tools 1.1.31117.00 Adds support for developing and debugging Node.js applications in Visual Studio

Node.js Tools - Profiling 1.1.31117.00 Support for profiling Node.js projects.

NuGet Package Manager 3.4.3 NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/ .

NuGet References 1.0 Save time by managing your NuGet links directly from Solution Explorer packages.config

PreEmptive Analytics Visualizer 1.2 Microsoft Visual Studio extension for visualizing aggregated resumes from PreEmptive Analytics Product.

SQL Server Data Tools 14.0.60311.1 Microsoft SQL Server Data Tools

StyleCop 4.7 Provides style tools and source code consistency. See https://github.com/Visual-Stylecop/Visual-StyleCop for more details.

TypeScript 1.8.30.0 TypeScript Tools for Visual Studio

Here are my debug settings:

Here are my project settings:

Here are the packages I use:

<package id="EntityFramework" version="6.1.3" targetFramework="net452" /> <package id="log4net" version="2.0.3" targetFramework="net452" /> <package id="Magnum" version="2.1.3" targetFramework="net452" /> <package id="MassTransit" version="2.9.9" targetFramework="net452" /> <package id="MassTransit.Log4Net" version="2.9.9" targetFramework="net452" /> <package id="MassTransit.MSMQ" version="2.9.0" targetFramework="net452" /> <package id="Newtonsoft.Json" version="6.0.6" targetFramework="net452" /> 

Other links not covered by nuget:

• The solution consists of two projects: consoleProject, classLibraryProject.
• consoleProject references classLibraryProject.
• When I go to debug-> windows-> Modules for classLibraryProject, I get the message "Could not find or open the PDB file.
• When I manually build a PDB for the LibraryProject class and move it to bin \ Debug for consoleProject, I get the "Loaded Symbols" character status. ** However, breakpoints are not respected. **
• Yes, I am sure that the code starts because the side effects of the code are visible.

How to make my control points work?

Answer 1

I just created a new console console + cool library. Make sure that in the console application there is a link to the class library (for example, in the image).

I wrote this because I do not see it on your screens.

Then right-click on the solution and select "Properties ...". You will see something like this: Make sure that the same configuration + platform is the same for your projects, and that the Build checkboxes are selected. If these checkboxes are selected, then after a “clean build” of your solution, you will see something similar in the bin \ Debug folder of the console application:

Please note: the class library has 2 files (highlighted on the screen): dll + pdb. In this case, dll + pdb are in synchronous state, and your violation points will work in the class library code.

If you do not have a pdb file for the class library project after the build, what could be your link to the class library, this is NOT a link to the VS project. Make sure that you correctly added the link (for example, to the image):

DO NOT refer to the class library DLL file directly through the Browse dialog.

You can verify that your console application is correctly installed in the class library project - open the csproj application console file during editing and look at the link:

If you have a BAD refence (in a .dll file):

than delete this link through the context menu in VS and add the correct one.

I hope this helps you.

Answer 2

You have my sympathy trying to fix it. When I compare settings with mine, I find 2 differences in debugging | Are common:

• check: disable JIT optimization when loading a module
• uncheck: load export dll

The first one can solve your problem.

Answer 3

There are various reasons why this can happen. I had the same problem and one of the possible solutions was to delete all the .pdb and .idb files.

Answer 4

Have you tried unchecking Debugging> General> Require that the source file matches the original version?

Answer 5

Just out loud, I came across the following, which does not mean debugging: These are general situations that are not related to any environment.

• The system runs on low memory, so the JIT does not go into debug mode. Increase, where possible, the memory settings for the server.
• Deployment does not replace the old version in any way, bypasses the script assembly and physically removes the artifact manually. Create a new artifact and expand it manually as well.
• Build scripts do not overwrite old classes / binaries, and they come from maven style cache or other storage. Delete links to these files and try again.
• Classes are being built, but they are not wrapped in the final object, delete the final object again and edit the assembly script to remove this error.
• Versions (some servers) do not allow you to deploy a new artifact, make sure that the version is deployed for deployment and try again.
• The server on which you are deploying is not located where you are connecting to a debugging session, or to the wrong port, or to other listening problems. Stop the server to make sure that the session is really where you think it is.
• Also from versions, if your dated artifact does not match the server date, for example, in an hour, for example, then it may not deploy again or deployments will be unstable.

If I think of others, I will be here.

Answer 6

I had this problem in code before. Try the following:

• Go to Debug -> Windows -> Breakpoints
• In the breakpoint window, click "Create" → "Break in Function"
• Enter the full name of the method.

This should at least give you a breakpoint at the beginning of the method, which you can then execute.

Please note that I always get an error message that tells me that the breakpoint will not work when I use this technique. But it still works.

Please note that I actually had valid characters loaded, so be sure to use your setting, which tells you that your characters are loaded.

Answer 7

I do not see where you are related to both processes. Visual Studio will by default attach only to the startup project. The console project seems to be your launch project. After you start debugging consoleProject, use the Debug menu and select "Attach to Process..." and select the process corresponding to the LibProProject class. Breakpoints will now be available.

Ctl+Alt+P is the hotkey for this.

Answer 8

I had a problem just like it was not so long ago ... and I'm not quite sure that from what I did, it really resolved the problem.

But what I can say is that I found that (although the packages.config entries looked fine), some (!) Libraries used were not in the correct version of .net ( net461 in my case).

I used a tool called Target Migrator to fix this. You can get it through Tools => Extensions and Updates => Online => Visual Studio Gallery

and then type Target Framework Migrator in the search box.

I remember that I also updated .Net to 4.6.1 during my attempts to fix the problem ... maybe you could try this too ... but in any case run Target Migrator for your own libraries (and restart VS 2015 along the way ) is definitely worth a try.

Good luck

Answer 9

Make sure your configuration is set to Debug, not Release.

Try, if indicated above: Tools-> Options-> Debugging-> Symbols and check "Microsoft Symbol Servers"

Answer 10

With such anomalies, it is worth clearing the solution (including manually deleting the bin and obj folders, then rebooting.