Debugging the code using F10 or F11 is not working(Step-over and Step-in not working as expected) - by Shilpa MSDN

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 634349 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 1/2/2011 10:42:54 PM
Access Restriction Public

Description

I'm debugging a Windows application in Visual Studio 2010 Ultimate. When i hit a breakpoint and press F10 or F11, then debugging just stops and the code continues without any more debugging (like pressing F5). The issue is not with the keys, because the F10 or F11 works fine for few lines and then suddenly the yellow disappears and the code runs further as if F5 is pressed, instead of debugging step by step.

I have raised this issue in msdn forum few days ago. Here is the link to it :

http://social.msdn.microsoft.com/Forums/en/vsdebug/thread/ab2ee4fe-de8f-4fda-991f-f4e70999ef9d

My code references Microsoft Office/Word 12 library
Sign in to post a comment.
Posted by Sphagnum Peat Moss on 4/11/2012 at 4:20 PM
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.

On a side note, also make sure that you're in DEBUG mode, not release mode, when trying to use F10 to step over.
Posted by Microsoft on 1/18/2011 at 6:20 PM
Hey Shilpa,

Thank you for reporting this issue. We believe we have fixed this issue in VS 2010 SP1 beta. Can you please try downloading the beta from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=11ea69cb-cf12-4842-a3d7-b32a1e5642e2&displaylang=en and see if installing that fixes your issue. I'm going to resolve this bug as fixed. If you still see the problem even after installing the SP1 beta, please reactivate this bug. Thanks again.

Marc Paine
Visual Studio QA Lead
Posted by Microsoft on 1/2/2011 at 11:22 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)