ehitek
asked on
The Breakpoint will not currently be hit. No Symbols have been loaded for this document.
Hello,
I'm working with VS 2008 on Vista Ultimate 32 bit.
When I try to debug my ASP.NET project, the breakpoints are not hit. The message is:
"The Breakpoint will not currently be hit. No Symbols have been loaded for this document."
I've found many discussions on this subject, so I've tried many things, nothing worked. I've tried to delete /bin and /obj folders, compile in the release mode then recompile in debug mode, checked the project properties and several other suggestions. Some posts mention checking the Module window under Debug menu, but I cannot find this window in VS 2008.
Some things to consider:
1. I have several projects on the same PC, only one has this issue.
2. The solution has only one project.
3. I'm debugging the server-side VB.NET code. Of course I'm using the debug mode, and Web.config is configured for debugging.
4. This is a very old VB.NET project written for .NET 1.1. It even doesn't have separate code pages, only .aspx. I imported it in VS 2008 and converted to use .NET 3.5. And it works fine, only debugging doesn't.
I would appreciate any suggestions on this. I think the problem is related to the fact that this project had been converted form .Net 1.1, but I don't know how to fix this.
Thank you.
I'm working with VS 2008 on Vista Ultimate 32 bit.
When I try to debug my ASP.NET project, the breakpoints are not hit. The message is:
"The Breakpoint will not currently be hit. No Symbols have been loaded for this document."
I've found many discussions on this subject, so I've tried many things, nothing worked. I've tried to delete /bin and /obj folders, compile in the release mode then recompile in debug mode, checked the project properties and several other suggestions. Some posts mention checking the Module window under Debug menu, but I cannot find this window in VS 2008.
Some things to consider:
1. I have several projects on the same PC, only one has this issue.
2. The solution has only one project.
3. I'm debugging the server-side VB.NET code. Of course I'm using the debug mode, and Web.config is configured for debugging.
4. This is a very old VB.NET project written for .NET 1.1. It even doesn't have separate code pages, only .aspx. I imported it in VS 2008 and converted to use .NET 3.5. And it works fine, only debugging doesn't.
I would appreciate any suggestions on this. I think the problem is related to the fact that this project had been converted form .Net 1.1, but I don't know how to fix this.
Thank you.
ASKER
Thanks. As I mentioned in my original message, I am compiling in the debug mode and web.config is configured correctly. I also don't make any changes to the code while debugging.
Delete the assembly from the GAC.
The information on this website will be helpful to properly delete the assembly:
http://blogs.msdn.com/alanshi/archive/2003/12/10/42690.aspx
The information on this website will be helpful to properly delete the assembly:
http://blogs.msdn.com/alanshi/archive/2003/12/10/42690.aspx
ASKER
Thank you, but I cannot open this site - The webpage cannot be found.
ASKER
OK, I opened it, will try this tonight.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you want to debug your code, make sure that the following are in place.
1. The project should be compiled in debug mode.
2. The current running project and the source code should be the same. If any modification done will not invoke the debugger.
3. Make sure that <compilation debug="true"> is set on the web.config