Why does F10 (step over) in Visual Studio 2010 not

Question

I also tried 2 solution. But It doesn't worked.

1. Go to Tools > Options menu in Visual Studio.
2. Go to Debugging > General menu item in left pane.
3. In right view you will see and option Step over properties and operators (Managed only). Uncheck this option and then you are all set.

and

1. Go to Tools > Options menu in Visual Studio.
2. Go to Debugging > General menu item in left pane.
3. In right view you will see and option Enable Just My Code (Managed only). Uncheck this option and then you are all set.

Answer 1

I had a similar problem on a Microsoft Ergonomic keyboard: F10 did not work as a step over for the debugger. Yet at the same time Fn-F10 worked on the Lenovo laptop. I found a resolution for the Microsoft Ergonomic keyboard: Press the Function lock key just to the right of F12. This is a toggle key that had the function keys turned off.

Answer 2

Turns out my issue was simpler/more embarassing, but I figured I'd post it just in case it helps someone else.

I had the F Lock (function key lock) turned off, so my F10 keypress wasn't being sent as such. With these newer keyboards (mine is an MS wireless keyboard), there are several modifier keys that affect the keyboard behavior.

Once I enabled F Lock, everything worked as expected.

Answer 3

I know this is an old issue, but it's one of the first search results for "Visual Studio F10 not working," so I wanted to post one possible solution here in case anyone else runs across this page with the same problem. My problem was caused by a very specific situation, so it might not work for everyone. The issue was the F10 shortcut simply was not working at all. Nothing happened when pressed. When I tried to reset the shortcut key for the Debug.StepOver, it wouldn't accept F10 as input.

SOLUTION: "Thaw" or uninstall Deep Freeze. I was using software called Deep Freeze to protect certain partitions on my hard drive. Unfortunately, Deep Freeze was protecting ALL of my hard drives, regardless of which drives I specified in the settings. When it was in "frozen" mode, it was causing crashes, hangs, and strange and erratic behavior in other programs including Visual Studio. When I rebooted in "thawed" mode, the problems went away and I regained the ability to F10 normally. Deep Freeze is commonly used on school and business computers, in which case you'd have to contact an administrator to deal with it, or alternately, set a different key combination for Debug.StepOver.

On a side note, also make sure that you're in DEBUG mode, not release mode, when trying to use F10 to step over.

Answer 4

Similar to the last post, I had another application that was open. So make sure all third party software is closed. In my situation I had installed CamStudio (screen recorder software). The moment I closed it I was able to start using F10 key again.

Answer 5

Hey I also encountered this problem. I was debugging a c++ project.

For people who still suffer from this problem, try changing the properties of "Devenv.exe" under the "Compatibility" tab to "Run as Administrator".

This solved it for me, I hope it works for you too.