Debugger stepping into non-user code

I had a hard disk crash a couple of weeks ago. (Yuck, but online backup really worked.) After reinstalling Visual Studio 2008, when I run an application with the debugger, going step by step (pressing F8) is causing the debugger to step into non-user code marked with <Global.System.Diagnostics.DebuggerNonUserCodeAttribute()>. I have the debugging option Enable Just My Code checked, which the documentation indicates should cause code with that attribute to be skipped.

I've tried unchecking and rechecking the Enable Just My Code box, which makes no difference. Any ideas on what may be causing this to happen? Anything other than holding down the Shift while pressing F8 to prevent the unnecessary steps?
LVL 20
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.

Miguel OzSoftware EngineerCommented:
This is a tricky one because we do not know how badly affected is your VS installation.
You can try resetting the environment as per the_mandril answer in this link.

Chances are you may need to repair or worst scenario reinstall VS2008 in this PC

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
ElrondCTAuthor Commented:
I tried resetting all the settings to the Visual Basic Development Settings, and it made no difference. I'd be more willing to do a reinstall if it weren't for the fact that the problem first manifested itself after doing a reinstall on a new disk. Interestingly, I found a saved settings file from last year, when I'm quite certain this problem wasn't present; importing that made no difference.
ElrondCTAuthor Commented:
Ended up needing to reinstall VS for a separate reason (enabling IIS and web services), and after the reinstall, the problem has gone away.
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.