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
smad007Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Fernando SotoRetiredCommented:
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.
smad007Author Commented:
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.
PMI ACP® Project Management

Prepare for the PMI Agile Certified Practitioner (PMI-ACP)® exam, which formally recognizes your knowledge of agile principles and your skill with agile techniques.

Fernando SotoRetiredCommented:
Have you looked in the bin directory of the project to see if the compiler created a file with an extension of pdb. This files holds the information for the debugger.

Have you tried clearing all breakpoints?

If the above does not work delete the bin and obj directories and re-compile the project.

Good Luck

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
smad007Author Commented:
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
Fernando SotoRetiredCommented:
Thank you very much for your comment. I am only happy that I was of some help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.