geekswithblogs.net

Doug Butscher

Nothin' but .NET!


News

Coders 4 Charities is live!!!
Add to Technorati Favorites

My Stats

  • Posts - 46
  • Comments - 118
  • Trackbacks - 33

Twitter












Tag Cloud


Recent Comments


Recent Posts


Archives


Post Categories


Image Galleries


Blogs I read


Company Links


Fun Stuff


Kansas City User Groups


My CMS Projects


<< Depeche Mode Concert Cancelled in Kansas City | Home | Superhero / Villain >>

The breakpoint will not currently be hit. No symbols have been loaded for this document.



I'm posting this blog mostly to remind myself how to fix this if ever I run into it again, but if anyone else benefits from it, then awesome.

In the Visual Studio IDE, when I set a breakpoint at a line of code, and start debugging, the breakpoint becomes that hollow maroon circle with a warning that says The breakpoint will not currently be hit. No symbols have been loaded for this document.

I've read a bunch of articles about makiing sure you're running in debug versus release mode, and making sure you deleted your obj AND bin folders. None of that worked for me. After some digging, and some help from John Alexander and Jeff Julian, I found one way that works for me.

  1. While debugging in Visual Studio, click on Debug > Windows > Modules. The IDE will dock a Modules window, showing all the modules that have been loaded for your project.
  2. Look for your project's DLL, and check the Symbol Status for it.
  3. If it says Symbols Loaded, then you're golden. If it says something like Cannot find or open the PDB file, right-click on your module, select Load Symbols, and browse to the path of your PDB.

I've found that it's sometimes necessary to

  • stop the debugger
  • close the IDE
  • close the hosting application
  • nuke the obj and bin folders
  • restart the IDE
  • rebuild the project
  • go through the Modules window again

Once you browse to the location of your PDB file, the Symbol Status should change to Symbols Loaded, and you should now be able to set and catch a breakpoint at your line in code.

I'm not really an expert on this, but I welcome any questions anyone may have, and I'll try to help out if you still can't get it to work.

Doug


posted @ Tuesday, June 26, 2007 9:57 AM |

Comments

Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Doug Butscher on 6/26/2007 10:03 AM
Afterthought: if you can't see the Modules window, I've seen that resetting your IDE gets it to show up. Go to the Visual Studio command line and type (without quotes) "devenv /resetsettings". Don't quote me on that, though.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Patrick on 6/27/2007 2:50 PM
Hey that worked! Been working on a compact framework project and half of my breakpoints worked and half didn't. I had to exit the IDE and delete all the bin and obj folders. Now my breakpoints work.

Thanks!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Dirty S. on 6/27/2007 2:54 PM
Great Post!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by tushar on 7/6/2007 5:56 PM
still not working on my site...i cant find module option on debug menu...tell me what to do plz..
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Doug Butscher on 7/7/2007 11:50 AM
Have you tried the devenv.exe /ResetSettings? This will restore Visual Studio to the default configuration. I never needed to use it, but I've see it bring back the module option on the debug menu.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Andrea Douglas on 7/24/2007 12:25 PM
Note: You actually have to select "Start Debugging" or F5 to see this window. Sounds obvious but threw me for a loop for a little while. You may be pointing to an old .dll that does not match your current build. This window will make all that very clear.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by ampad on 8/19/2007 7:06 PM
One gotcha I ran into, if you inadvertently change the Properties->Linker->Debugging option "Generate Debug Info" to No; building the Debug configuration will generate a PDB but the DLL not have any symbolic information. This will show up in the Debug->Modules window as a problem...something to the effect of "does not contain symbolic information"
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Jitendra MIshra on 9/7/2007 5:31 AM
Hi Doug,
I am not able to see my dll in the list of modules window .I tried by flushing the obj and bin folders, But still not working 4 me
Plz tell me wht 2 do?
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Yaqoob Johnson on 9/13/2007 6:12 AM
Hi Doug,

Tried your suggestions and they didn't work so was getting desperate. Eventually fixed it by checking "Use fixed naming and single page assemblies" in the MSBuild section of the web site property pages. Don't know why that fixes it, but boy am I happy it does!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Jovis on 9/19/2007 9:03 PM
If you are doing web development, simply do the following:

1. Close your Visual Studio.

2. Go to the Temporary output folders and remove all the files inside it.

The folder format is something like this:
C:\WINDOWS\Microsoft.NET\Framework\{framework version}\Temporary ASP.NET Files\{some name}\{some numbers}\{some numbers}
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by D Walker on 10/2/2007 12:02 PM
Brilliant. Thank you very much. The modules window allowed me to see that my solution was using a different version of my DLL so although I was unable to reload symbols in that window, I was able to delete the rogue DLL and the problem was fixed. Turns out the rogue DLL was in the "Shadow Copy Folder".
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by sreejesh on 10/3/2007 12:41 PM
Thanx very much..Its working fine. all the break points are being hit. thank you.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by NightCrawler on 10/8/2007 7:10 AM
i am unable to spot out my dll name in the list of modules,...... please do help !!!!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by zach on 10/19/2007 12:20 PM
Thanks, Doug, this is all good info. I have a solution that contains 2 web sites in it (along with a dozen server side components) and I can only debug whichever project is set as the startup project. So when I transfer between sites I can no longer debug. Does anyone have any idea as to why this happens and how I can fix it.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by cporter on 10/23/2007 8:05 AM
I found that, if you have a winforms project and you are calling *any* unmanaged or mixed-mode dlls, you must set the startup project to allow unmanaged code debugging. I am assuming that it would be the same for a web solution. (Properties - Debug - Enable Unmanaged code Debugging).
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Matt on 11/13/2007 2:50 PM
When trying to do the 3 steps listed above I was getting a message about the PDB file not being compatible or something. The solution was finally reached when I deleted the exe off of the emulator...then it worked for me.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by RG on 12/11/2007 10:34 AM
I read on another site that the problem was to do with the framework on the target device. I'm working with the compact framework so the easiest way to reinstall the framework was to do a hard reset on the device and deploy from visual studio again. This has worked for me when all of the above failed.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Mythili on 1/9/2008 10:50 PM
I tried all these above options (except re-installing visual studio as it's not an option for me) but none worked for me. I tried this on two machines and still have the same problem (cannot hit the break points I set in the code). I have an application containing 5 projects. Any help would be greatly appreciated. Thanks.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by RBenak on 1/10/2008 1:46 PM
I recently inherited support for a VS2003 solution with 8 child projects where I can set breakpoints in the start-up project but none of the other projects (The breakpoint will not currently be hit....). The debug directives are all in place and the .pdb files are being generated in the bin folder of the local project directory. The module window displays all referenced assemblies, however, all assemblies except the start-up assembly information field indicates that 'No symbols loaded' and the assembly path is pointed to c:\documents and settings\.... An attempt to 'Reload Symbols..' fails silently. The path is simply not updated. Quite a headache for (what seems to me) a fundamental issue. Any Ideas?
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Yogesh Diwan on 2/15/2008 7:35 AM
I was also having this problem. I am using Visual studio 2005 express edition. The problem is fixed by following steps.
1. In Project Properties -> Configuration Properties -> Linker -> Debugging, 'Generate Debug Info' is set to 'Yes'.

2. In Project Properties -> Configuration Properties -> C/C++, 'Debug Information Format' is set to 'Program Database/ Zi'.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by thctase on 2/19/2008 6:12 AM
ONE solution with multiple project solution.

If you have 3 or more project is necesary that the initial proyect reference AND USE declaring at least one type of all the projects that you need to debug. If the .Net compilers detect that you are not using a pryect directly from start proyect the compiler dont generate de debug information.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by SoG on 2/21/2008 3:11 PM
Although none of the posts helped me directly, Cporter helped saved my bacon hands down. Thanks a mill. Instead of setting the debugger to unmamaged only I had to switch it Debugger>Debugger Type to 'managed only'.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by K on 2/22/2008 2:12 PM
Yogesh Diwan: Thank you!

That clinched more than a day of fiddling with eclipse and visual studio to simultaneously use them to debug JNI and native code.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Carlos Mendoza on 2/28/2008 1:15 PM
Ok guys, just go to BUILD --> CONFIGURATION MANAGER, and set the Configuration field to DEBUG and not to RELEASE, that worked for me.
Hope this helps.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Juan Carlos on 3/4/2008 5:00 PM
Doug, you r the best, it worked out, and i don't have the problems with those messages.

Also I have to un-check the "Enabled Optimizations"..

Thks
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by web servicer on 3/11/2008 7:57 AM
hey guys,
working on a webservice and to test it ive added another project to the solution. i can debug the test app fine but when i try to debug the webservice code i get the infamous error msg. i tried everything ive seen online- wiping out bin and debug folders, running in debug mode, etc and i ran your suggestion doug and nothing! im not sure if web service code behaves differently. any suggestions guys would be appreciated. ill get back to trying to figure something out now. thanks in advance.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by web servicer on 3/11/2008 8:08 AM
one more point the dll for my webservice doesnt even show up in the module list. ??
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Doug on 3/11/2008 8:25 AM
Mona,
Where is your web service running? Locally or remotely? Do you have remote debugging installed if you're running remotely? Are you in VS 2003, 2005, 2008? 2005 and 2008 will host your web service for you. Can your test app even connect to the web service? Are you sure it's running? If the dll isn't showing up in your modules list, that usually means the CLR isn't even running that code. When it runs the code (but can't find/map the PDB), your dll will show in the modules window, but it won't load the symbols.

I hope some of these questions lead you to your answer.

Doug
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Heisa on 3/12/2008 4:35 AM
Hello,

I am trying all the solutions, but it still isn't working for me.
What I find strange is, when I look at the module information, it says the DLL resides in the GAC...
But my pdb file is in the bin directory of the project...

I cannot load then pdb from the bin. I receive the following error: The symbol file ... does not match the module.

It is getting pretty annoying now :(
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Heisa on 3/12/2008 5:11 AM
Hello again,

Finally solved it...
pfff

I deleted the assembly from the GAC.
The information on this website was also very helpful to properly delete the assembly:
http://blogs.msdn.com/alanshi/archive/2003/12/10/42690.aspx

thx!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Tyler on 3/15/2008 6:38 PM
Yogesh Diwan - That worked for me! Thank you thank you thank you!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Matt D on 4/3/2008 3:39 PM
Thanks! Deleting my BIN and OBJ folders did the trick. :)
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Deepani Perera on 4/10/2008 4:20 PM
That worked. Thanks !!!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Jason Haley on 4/17/2008 10:54 PM
Thanks for this post ... fixed my problem!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by John on 4/25/2008 10:46 AM
I was having similar problems with the debugger not working for a web application. Vista Ultimate (IIS 7), .NET 2. None of the above worked for me, deleting bin and obj folders etc etc. All the symbols were being loaded but the debugger just didn't want to hit a breakpoint. I finally gave up the ghost, created a new solution and added all the files from the old solution to it. This worked. This made me wonder what was different... the code was the same. I then noticed that the old web site was running in a Classic .NET AppPool. Switching it back to DefaultAppPool solved my problem. Hope this can help someone else out. I've got very little hair left after this!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Ignace on 5/8/2008 5:53 AM

Closing VS and rebuilding the project did it for me, thanks!

MSFT please add the entire list of posts into your MSDN knowledgebase, it truely helped me!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Matt M. on 5/13/2008 1:55 PM
I've checked that it's in debug mode, not optimized, and I've added the .pdb to the location on the server that I'm running my Windows service from. The service had been uninstalled. I cleared the obj and debug folders on my machine, rebuilt the project, took it over to the server and installed the service there. I retained the .pdb that had just been built.
I see this in the symbol load information: <Server Location>\Service.pdb: Cannot find or open the PDB file.
<Local Location>\obj\Debug\Service.pdb: Symbols loaded.
No native symbols in symbol file.

I also directed the IDE to the pdb but received "the symbol file ____ does not match the module". Any ideas?

Only thing I haven't been able to try is what "Matt" above said... "deleted the exe off of the emulator". I'm not sure what that means.

Thanks all!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Raphael de Bem on 5/14/2008 3:35 PM
If in a project a file is missing, the debug not work! For example you add a file to deploy with your application and delete these file but not remove from project.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Ken on 5/15/2008 4:04 PM
If this is a web application, make sure your page directive has the following.

AutoEventWireup="true"

I had a .Net 3.5 solution with 1 web project and 7 classes that would not debug on any pages where AutoEventWireup="false".

Before migrating to 3.5, the web pages for that project would debug in VS 2003 under it's original .Net 1.1 environment. Once it was in 2008, any web pages with that directive set to False refused to debug.

This may not be the "correct" answer, but it fixed my issue.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Mattias on 5/18/2008 3:42 AM
I had the same problem.. not being able to debug my silverlight project. But the only thing I did was.. right click on solution - property pages - start options - in the debuggers area make sure that you have both Asp and silverlight selected./ hope it helps
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by developer on 6/4/2008 4:51 PM
i have a similar problem, symbols not loaded. the modules windows gives location of the file as GAC folder, but i dont find a folder like that in my assembly in the windows folder on c drive. please help me on this...this is troubling me a lot...thanks
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by developer on 6/4/2008 4:54 PM
i have a similar problem, symbols not loaded. the modules windows gives location of the file as GAC folder, but i dont find a folder like that in my assembly in the windows folder on c drive. i have tried all the things told above, but none helps...
Gravatar # The breakpoint not hitting in asp.net web applications
Posted by developer on 6/20/2008 1:27 AM
while loading asp.net web application pages , breakpoint is not hitting in page_load, but its working in asp.net windows application, i am using vista enterprise edition
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Bino on 6/29/2008 11:02 PM
Perhaps the only thing we can do is like,if we have multiple projects loaded in our solution then hitting the breakpoint on another project in the same solution unless its not set as the startup project will sometimes return this error. so what we need to do is to set our current project as startup application where we want the breakpoint to be hit.thats it.per se .Net 2005 :)

www.codepal.co.in
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Greg on 7/1/2008 3:30 PM
I have been running into this problem with a web application that utilizes several web services. These webservices are not part of the application actively being debugged yet I want to step through the code to see what is going on. I was able to get the breakpoints to load by browsing to the webservice through my browser. I have not yet been able to step through the code. Any thoughts?
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Tony Diering on 7/4/2008 1:47 PM
Thanks. THe option to display the Loaded modules was very useful. It showed that the DLL was being loaded from another folder (data folder) and was thus not the latest rebuilt dll. Debug-->Windows-->Modules is a very useful menu item.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Shaul on 7/9/2008 3:44 AM
Thank you!
All I had to do was blow away the bin and obj folders, and everything was fine. The tip about the Modules window was great - turned out I had a dll from 2006 that for some reason wasn't being rebuilt!!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Hatim on 7/25/2008 5:52 AM
I had the same problem guys but the reason was that the linker output directory for my dll module was not the same as the project bin directory(looks like it was changed). So the Project was using an old version of the dll.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Dutt on 7/29/2008 6:28 AM
but mien is huge project. bin directory contains lots of DLLs. I can delete all.

But i have tried deleting the specifi DLL. break points are not working. Anyidea on this?

Error:
The breakpoint will not currently be hit no symbols have been loaded for this document
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Farooq on 8/4/2008 4:49 AM
Thanx for giving valuable tips its working for me
I have removed bin folder and obj folder
and rebuild the application
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Dracore on 8/11/2008 12:41 PM
I tried all of the above mentioned and nothing worked but then I discovered something new! My solution consists of 2 projects: One C++ (OCX/DLL output) and one C#

I wiped all my bin/obj folders and everything but still no luck. Debug mode + No optimize + Debug Unmanaged + Generate Debug Info YES. My modules were all up to date. No errors.... still nothing

Then just now I went into my C++ properties>Debugging>Debugger Type, it was set to Auto. I changed it to Mixed.

Ran the project and immediately I hit the breakpoint in my C++ module.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by KooKooBung on 8/13/2008 10:53 AM
Go into the advanced compile options for that project and make sure that 'Generate debug info:' has a pdb file being created.

I was receiving the wrong version errors and this was the solution. Breakpoints work now.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Gabriel on 8/21/2008 12:40 PM
Be sure that in website PROPERTIES page in tab WEB, section server is pointing to the path that files are being build. In my case the files were being built in folder "A" but the IIS Web Server/Project URL was pointing to folder "B". Normally it still works because in folder B there is old compiled files for the same project.
;)
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Mayank Parmar on 8/27/2008 12:59 AM
Hi Ken,
Thanks this worked for me.

>Posted by Ken on 5/15/2008 4:04 PM
>If this is a web application, make sure your >page directive has the following.

>AutoEventWireup="true"
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by RG on 9/1/2008 3:49 AM
I posted above about reinstalling the compact framwork but we had another instance where this didn't work.

In this case we found that the registration of System32\OLE32.dll had been messed up by another application uninstall. We only noticed this as we couldn't successfully drag a file off of a device to the desktop using active sync.

By re-registering this dll the communication problem went away and debugging returned.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Dave D on 9/12/2008 3:09 PM
The only way I could debugging to work again was to switch from Cassini to IIS.

:)
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Rinku on 9/17/2008 3:32 PM
None of the above solutions helped me. I deleted my obj and bin file and rebuilt the project but it failed.
In the module window under debug when I try to load symbols, it gives me error "The symbol file does not match the module.

Some one please help me.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Tony on 9/19/2008 4:37 AM
The problem lies in the Configuration manager.
In debug mode you can set it to actually compile in release mode. Be sure that the Debug configuration is set to debug mode and not releas mode.
Voila
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by sr on 9/23/2008 5:12 PM
If there are any references to dlls which you added, go to solution explorer, delete these references.
Do not delete any System.* references.
Save your solution.
Now add the references to dlls which were build in Debug mode and rebuild your solution.
And of course do all the suggestions others have adviced in the Project-Settings. This should now load the symbols and would help in Debugging.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by AshishBanerjee on 9/26/2008 7:31 AM
Hey dough with reference to blog where in u ask to nuke the bin and object folder, i am asking
to please elaborate that point.actually i think that the bin folder contains the references and what is the obj folder?please explain me .i m very new to vstudio + .net combination. i m ferering ur blog for the debugging symbol not hit.not solved yet...
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by LK on 9/29/2008 6:24 PM
Hi all,

Great article, and I tried everything. I basically got stuck at the same place Matt M. described on 5/13/2008. Did anyone ever solve that problem?

Thanks!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by FSidd on 10/13/2008 11:04 AM
Hi all,
I had similar problem while attaching to another process the breakpoints were not hit. I realized that Debugger type auto was selected. At the time the process was attached it would pickup the type "managed" as I was attaching a vb6 process.
I changed it to debugging type native as my code base was un managed c++.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by J Al on 10/16/2008 12:28 PM
Amazing. Thank you so much. As yourself, I will keep a note to your blog to remind myself when I forget!
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Brett Jones on 10/20/2008 12:17 PM
Thanks, this got my brain juices flowing!

I had made a copy of the default.aspx file and the CodeBehind was "copy of default.aspx.cs". But, I had deleted the "copy of default.aspx.cs" file so wasn't finding the correct code. I changed the codebehind to point to the correct default.aspx.cs and it's working now.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Jatin on 10/23/2008 1:16 PM
None of the above fix work for me.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Jatin on 10/23/2008 1:29 PM
I am not able to see my application.dll into Module windows. I have 10 projects in my solutions and project i am trying to debut is web project. I can debug other projects under solutions.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Joris on 10/31/2008 2:42 AM
Thnx, i forgot to set the project in Debug mode.
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Pete Austin on 11/12/2008 9:00 AM
An alternative approach to debugging is to add lines like the following into your project. Yes it's clunky, but it forces the POS development environment to break. When it breaks, you can add other, conventional breakpoints.

#if (DEBUG)
System.Diagnostics.Debugger.Break(); // DEBUG
#endif
Gravatar # re: The breakpoint will not currently be hit. No symbols have been loaded for this document.
Posted by Justin on 11/13/2008 11:50 AM
Thanks! This tip helped me out!
Post a comment





 

Please add 3 and 7 and type the answer here: