Menu
I also tried 2 solution. But It doesn't worked.
and
890
F10 ("step over") does not descend any further into the call stack. It moves to the next line of the current function. F11 ("step into") drills down into the function being called. If you hit a breakpoint on function2() , F10 will advance to the line function3() .
Check if you have function lock key -- 'F Lock' key on keyboard. If so then try pressing it once and then press F11 for debuging. Alternatively you can verify the working of F11 outside Visual Studio using it on IE or other windows and keying F11 , this should maximize the window. F Lock it is.
In most languages supported by Visual Studio, you can edit your code in the middle of a debugging session and continue debugging. To use this feature, click into your code with your cursor while paused in the debugger, make edits, and press F5, F10, or F11 to continue debugging.
CamStudio application was the issue in my case.
Somehow it reserved this key to itself and Visual Studio was not able to use it anymore (I've tested it MS Word (Alt+F10 - was working as expected, while CamStudio was on - when minimized it appears only in SysTray)).
I've closed CamStudio and it was fine:
F10 functionality "reappeared" in VS2008.
150
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.
43
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
