Breakpoint Will Not Be Hit No Symbols Loaded Dll
Randolfo Rasberry
It fixed the problem for me temporarely when I deleted myProjectFolder. But it still points to this .pdb - file (VS recreates the temporary folder after deleting). I guess it should point to the .pdb in the bin-directory though, as it does in other assemblies. How am I supposed to fix this? Or is this a normal behaviour?
Edit: It is an ASP.NET - Project (.NET 4.0), MVC 3. No COM-libraries included so far. I have now deleted the above mentioned directory again, and ended up once again with The breakpoint will not currently ...". If I open the Modules-window, Symbol Status shows "Skipped loading simbols." for all assemblies, except for App_global.asax.exot9a5x.dll.
Another solution to the break point issue with a javascript file is to clear IE9 cache. I ran into this issue after updating/saving a js file. Visual Studio 2012's debugger will not update the .pdb until I went into Internet options and deleted the temporary internet files. Hope this will save someone some time.
Turns out, that during those installations somehow, my publish settings lost the specific port that I was running the dev project on. Being that I was so used to that port number for the last 4 months, I didn't even think about it, but the whole time I thought I was looking at the dev machine, it was not actually running on that port, and I was looking at cached pages that were already up in my browser. DER!
What helped me to find this solution has been looking at the Modules windows while debugging and saw that for my ASP.NET DLLs loaded I had: Binary was not built with debug information.
When I set a breakpoint in my class library project. It appears as a normal breakpoint. When I start debugging my solution the breakpoint becomes hollowed out and has a yellow triangle with an exclamation point inside. The tooltip displayed when I pan over the breakpoint is, "The Breakpoint will not currently be hit. No Symbols have been loaded for this document."
I have taken over an existing winForms application with multiple projects in the solution. I have the project built and running in debug mode. I can stop at breakpoints in some projects but, I am unable to hit the breakpoints in other projects specifically my project that is of type class library.
All of the posts I have read have been very informative, but none of the suggested solutions have fit my specific needs. Please let me know if more information is warranted. I have more links I can provide as references to what has not worked. As well as additional steps I have taken to attempt to solve this issue.
My project is an ASP.NET application, but the base problem will happen on WinForms as well. The problem arises when a DLL is missing from the assemblies output. However, this same exception occurs if the DLL you are referencing then references another DLL that is not in the assemblies. Due to the way the operating system loads DLLs, the referenced DLL must be in the environment path, and not in your output assemblies.
The core cause to this problem is in the way the operating system loads native DLL's at >runtime. Native DLL's are loaded using the following logic which does not include the >Temporary ASP.net Files nor the applications /bin folder. This problem will also occur in >any .Net application if the Native DLL is not included in the /bin folder with the .EXE >file or if the DLL is not in the Path Environment Variable.
I was using a DLL called DivaAPIWrapper.dll (Managed DLL for C#). I knew, however, that DivaAPIWrapper.dll needed DivaAPI.dll (Unmanaged C++) to operate. I placed DivaAPI.dll in all my output paths but I kept receiving this error. Only after I placed DivaAPI.dll in my environment path (C:\windows\Microsoft.Net\Framework\v2.0.50727) did it work. Please note: your path may be different if you're using a newer version of the .NET framework!
I have this happen all the time, like you said the breakpoint is not active until the DLL is loaded. It really doesn't matter though, because it has to load the DLL before the code can get to that point anyway. My breakpoints start this way but they always get hit.
Check that you didn't change the processor at which you aimed to compile this project. I had, and when I changed it back, everything worked again. Apparently a change in processor makes it 'different than the original'
I had the same Problem with VS2008 in a Vb.net-forms application where I called a dll in another project, loaded in the same project group. I found this simple solution: I loaded an instance in the form_load event like Dim pmg As New PMGExport.PMGExportNeu.
I have two Windows Forms projects in the solution. One of them loads the debug information, one doesn't. They both refer to the assembly I'm trying to get debug information on in exactly the same way in the project file. Any ideas?
I want to add here, mostly for myself when I come back to review this question, that symbols are not loaded until the assembly is loaded, and the assembly is not loaded until it is needed. If the breakpoint is in a library that is only used in one function in your main assembly, the symbols will not be loaded (and it will show the breakpoint as not being hit) until that function is called.
Start debugging, as soon as you've arrived at a breakpoint or used Debug > Break All, use Debug > Windows > Modules. You'll see a list of all the assemblies that are loaded into the process. Locate the one you want to get debug info for. Right-click it and select Symbol Load Information. You'll get a dialog that lists all the directories where it looked for the .pdb file for the assembly. Verify that list against the actual .pdb location. Make sure it doesn't find an old one.
In normal projects, the assembly and its .pdb file should always have been copied by the IDE into the same folder as your .exe, i.e. the bin\Debug folder of your project. Make sure you remove one from the GAC if you've been playing with it.
Just something simple to try - you may have tried it already. Right click the Solution in solution explorer, click "clean solution", this deletes all the compiled and temporary files associated with a solution.
Then I set that to "Debug" and it started to generate the .pdb file. BUT I need to manually copy the PDB and DLL and put in the folder that VS was looking (here is where the selected answer helped me):
Check if your .pbd file is missing in your bin/Debug folder. If it is then go to "Properties" of your project, selected "Build" and then "Advanced" at the bottom. Choose "full" under "Debug info" in the new window that appeared. This was my issue and solved it for me.
We found the cause of our problem. This code was using the "CodeBehind" attribute in the Page directive of the .aspx file instead of the "CodeFile" attribute (ASP.NET 2.0 and beyond). After days of desperation, a simple search and replace solved the problem.
The .dll where I want to stop debugger and the associated .pdb files where copied near the .exe file. Those files had an older date so I thought they weren't updated in the runtime. I manually deleted them, Visual Studio create another pair AND put this new pair near the .exe. Now the breakpoint works!
Once this code is reached, an exception is triggered and .NET Framework shows a dialog box asking which Visual Studio (i.e. new instance of VS 2008, new instance of VS 2013, etc) you want to use to debug the program.
this happened to me after copy paste another webservice asmx file into an existing webservice, resulting in the same error when trying to debug the recently added service, to be able to debug I had to start without debug, then attach to the process. its weird but its the only way i found to be able to debug.
I am trying to debug a BPM using Visual Studio. I am able to attach to the w3wp.exe file on the Epicor server. When I go to set a breakpoint I receive the message:
The breakpoint will not currently be hit. No symbols have been loaded for this document.
I misread the settings for the debugger Options. Enable Just My Code and Require source files to exactly match the original version must be UNCHECKED. I had them checked which was my problem. Symbols now load and debugger breakpoints now work.
On the server try the command and see if you get the process. I got the process ID, but then when I attach it to Visual studio, the break point will not hit. I think it maybe because of Visual Studio 2017. Next thing I will try is Visual...
Thanks for your help Toby.
It seems that VS shows the error with no symbols loaded until the piece of code has been reached while the debugger is running. I had done all the right things except for performing the action to call the method that I have the extension on.
I am getting a problem setting debugging breakpoints in Javascript, hovering over the breakpoint I get the tooltip: "The breakpoint will not currently be hit. No symbols have been loaded for this document."
Is it just this page it happens on? If you can try to render that empty view and breakpoint hits then it's something in code silently failing. I had an issue like this where my site and code was working without error even though I had syntax slightly incorrect somewhere. It seems code was good enough for compiler but debugger just ignored error instead of throwing it which made it not hit break points for some weird reason.
Any time I get in a situation where I cannot understand what is causing an issue I usually create a fresh project and check everything is working. Then I add things in one by one until the error is replicated. You have to try and isolate whats going on.
OK was just silly mistake at my end I got it working again. Interesting thing to note is that it gives that error that breakpoint wont be hit right up until it gets hit so it may well be logic issue in your app I dont know.
I'm working on an add-in for ArcGIS Pro, and I am having some trouble hitting breakpoints in my code when debugging via Visual Studio. I am receiving a warning stating "The breakpoint will not currently be hit. No symbols have been loaded for this document."
7fc3f7cf58