The breakpoint will not currently be hit. No symbols have been loaded for this document
- I have now wasted 8+ hours trying tot fix this problem. I have read many of the dozens of threads already related to this issue and I have not solved the problem.
Situation:
- VS 2005
- .NET 2.0
- Windows Server 2003
- Project is on my local machine, database is on a remote server within network
- This is not a web service or a hand-help application, it's just a plain old data-base driven website.
- I am in debug mode
- I have deleted all files in the Temporary ASP.NET folder multiple times
- The problem is not related to the machine.config file
- I am quit certain it is NOT an IIS problem (keep reading)
- I have un-installed the 2.0 framework and VS 2005 and re-installed both
- I have done EVERYTHING that other people have suggested. NOTHING has worked.
'WebDev.WebServer.EXE' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll', No symbols loaded.
When looking in the TEMPORARY ASP.NET directory, there are SOME .pdb files, and all of these load correctly when trying to debug. Not suprisingly, however, in each case where the output window says "No symbols loaded" there is no .pdb file.
I just can NOT spend any more time on this. For the love of God, can someone help? All I want to do is hit break points when I de-bug. Is that so wrong?
ccrookston
답변
Even I had the same problem. I solved this by following these steps,
1. Goto Tools, Internet options and Clear the History.
2. Clear the Temporary Internet files.
모든 응답
Try including web deployer project in your solution. Deploy using that. In options of deployer, make sure you are creating single dll for your web project. Then try debugging it.
I had faced kinda same problem. What I did was the same I said above.
It was strange, I tried deleting all the temp files and it was still loading without symbols. Well, do try deleting all the cache and temp files related to your application. You might need to navigate to your ASP.NET assembly cache folder. Make sure the debug is true in your config file.
Hope above helps you.
- I downloaded and installed the Web Deploy Project.
Still nothing. My anger is reaching boiling point. Is there nobody from Microsoft on these forums who can provide some answers? MANY MANY people are having this same problem. Ug. I'm so pissed off. - Have you tried deleting the temp files which may be there under your profile?
- Yes.
check the IIS version
go to IIS, select your project,open properties,select 'asp.net' tab check the version, if you different version installed just try another version. this helped me once
- You may not be able to debug anything which is in the GAC. So check the GAC to see if your DLLs are there. If so, remove it.
Please check solution properties (Not project's). change "Active config" to "Debug| Any CPU".
i had similar problem as reported by you. This change worked for me.
Regards,
Harkawal
- I've had the same problem, and have tried every suggestion posted in this forum--wiping out temp asp.net files, stopping and restarting iis, checking all config settings to be sure I'm in debug, etc. No luck! I have no problem placing breakpoints in any code located in non-web projects in the solution (business layer, DAL, etc.). But the web project code behind files are not supporting breakpoints. Anyone come up with other ideas to try yet? Thanks!
Delete .suo files related to your project/solution and try again. These files might be hidden.
I hope this will work for you
Had exact same problem in an app that I created from scratch in VS2005. Fixed by changing the default Server from "Visual Studio Development Server" to "Use IIS Web server" from the project's Properties->Web tab. Note this requires you to have IIS installed.
In another instance of an app that I ported from 1.1 to 2.0 I had to open the "Advanced Compiler Settings" from the Compile tab on the properties window and set the "Generate debug info" value (set to pdb-only or Full). Not sure why this was NOT set by default. My 1.1 apps were all set up for debugging.
Glad it's finally working and hope this 4 hours of searching saves you some time.
Well, since my original post which started this thread, I have completed the project which I could not (and still can't debug.) I tried everything that everyone here suggested - thank you all for your input. That project was migrated from 1.1 to 2.0, and I am now just convinced that that particular app will never have debugging. I have started two new projects from scratch and both of them hit break points just fine.
So, today's lesson: don't migrate a project from 1.1 to 2.0 and expect to debug.
I am still working on the same project that I was working on when I posted my comments about a week ago, stating that breakpoints placed in code-behind files in aspx pages were not being hit. Those same files now are supporting breakpoints. Just a couple of days ago, I started experiencing considerable slowdowns on my PC. I discovered that there were problems with my harddrive. I did some cleanup, including running the chkdsk utility. At first, some of the breakpoints would not work, but then eventually start working right while the app was running! Now they get hit every time. My moral of the story--debugging problems like those mentioned in this thread could on occasion be caused by hard drive problems--corruptible files, including some used by Visual Studio (.pdb files, .dll's, etc.). Check your harddrive--it may be the culprit once in a while.
I too wish to thank everyone for their input. I've learned alot during this experience.
I had this issue in a VB 2005 mobile project. I fixed it simply by opening windows explorer, go to your Debug folder as noted below
ProjectFolder >>>Bin>>>Debug ------------------delete everything in here.(trust me)
THEN Go to this folder:
ProjectFolder>>>Bin>>>Release------------------delete everything here too.
After you do that from you project within VS 2005 IDE go to those same folders and delete those until those two folders are empty.
NOW, make sure your settings in the Project Properties (right click project in Solution Explorer within VB IDE and click properties) on the Debug tab, make sure it has DEBUG selected and not RELEASE. Last thing is rebuild your project. You should have success in the rebuild, then set a breakpoint and try to debug to see if it works. I did all the above and had it fixed in 5 minutes.
Even I had the same problem. I solved this by following these steps,
1. Goto Tools, Internet options and Clear the History.
2. Clear the Temporary Internet files.
Came across same problem, the poject involved converting an app converting from 1.0 to 2.0 framework. Following steps worked for me. Hope it helps somebody out.
In VS 2005
Build>Configuration Manager
I changed the Active Solution Configuartion to Debug.
after that program excution stopped at the break points. Not sure if this will help ccrookston
- Is there still no true fix to this? I have spent several hours on this. My debugger all of a sudden stopped working for no apparent reason. I have tried everything in this thread, and it still doesn't work. I am using VS2008.
- This seems to be a recurring theme with VS2005.
I have been trying for days to correct the same issue
"The breakpoint will not currently be hit The specified module has not been loaded."
I have tried every solution shown in this and other threads and still cannot get it to work.
I've even tried a solution that will debug and loaded into it the VB code pages only from my solution that will not debug and it has stopped working.
So come on Microsoft tell us which module has not been loaded, and just how to load it correctly, it cannot be a coincidence that a lot of people are complaining about this, give us the solution please.
