smad007
asked on
The breakpoint will not currently be hit
I've seen variations of this annoying debugging problem, but none of those discussions have helped.
All of a sudden when I start debugging my program the breakpoints turn into clear circles with little question marks in them and they no longer work. When I float the mouse over them I get a message saying "The breakpoint will not currently be hit. The source code is different from the original version." The message then goes on to suggest that to fix the breakpoints I should "Right-click on the breakpoint and choose 'location'...(ect.)", well there is no 'location' option when I right-click on the breakpoint. This helpfull message says that alternately I could "disable the option 'Require source files to exactly match the original version' under Tools, Options, Debugging, General. So I go to Tools, Options, and guess what...there is no Debugging (you gotta love beta releases).
Has anyone come across this before? It will get very frustrating using this wonderfull, slick VB.NET IDE if I can't use the debugger!
Please Help,
Adam
All of a sudden when I start debugging my program the breakpoints turn into clear circles with little question marks in them and they no longer work. When I float the mouse over them I get a message saying "The breakpoint will not currently be hit. The source code is different from the original version." The message then goes on to suggest that to fix the breakpoints I should "Right-click on the breakpoint and choose 'location'...(ect.)", well there is no 'location' option when I right-click on the breakpoint. This helpfull message says that alternately I could "disable the option 'Require source files to exactly match the original version' under Tools, Options, Debugging, General. So I go to Tools, Options, and guess what...there is no Debugging (you gotta love beta releases).
Has anyone come across this before? It will get very frustrating using this wonderfull, slick VB.NET IDE if I can't use the debugger!
Please Help,
Adam
Fernando Soto
This could happen if the config for the project is set to Release. To check if it is got to menu bar click on Build->Configuration Manager..., in the new window make sure that the Active Solutions Configuration is set to Debug.
Have you upgraded to the .NET Framework 1.1 and the IDE to Service Pack 1?
http://msdn.microsoft.com/netframework/downloads/default.aspx
http://www.microsoft.com/downloads/details.aspx?familyid=c41d8159-b42f-4d06-a797-e510494976ee&displaylang=en
http://msdn.microsoft.com/netframework/downloads/default.aspx
http://www.microsoft.com/downloads/details.aspx?familyid=c41d8159-b42f-4d06-a797-e510494976ee&displaylang=en
ASKER
Thanks for the comments but the solution is still elusive. The project is set to Debug, not Release, so that is not the issue. And I am actually running VB.NET's beta 2 release so I don't think GivenRandy's suggestion will help me.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks to FernandoSoto. I deleted the bin and obj directories, opened the project and ran the debugger and the breakpoints work!
Just thought I'd point out that of the three questions I've had acceptable answers for since joining EE, Fernando has given the accepted answer for every one of them. I think Fernando deserves an entry in the top 15.
Thanks again
Just thought I'd point out that of the three questions I've had acceptable answers for since joining EE, Fernando has given the accepted answer for every one of them. I think Fernando deserves an entry in the top 15.
Thanks again
Thank you very much for your comment. I am only happy that I was of some help.