Occasionally these programs are somewhat tricky for my students to use, so when this happens, I create a simple video for my students to watch to introduce the programs. Hope this helps someone else.Once in a while I have a new application, web applet, or web site I want students to use. As I read through all the above solutions and didn't find anything helpful, I suddenly remembered seeing the attribute. I could set breakpoints on individual lines and the debugger would stop, but that was getting to be a nuisance. That's when I discovered I couldn't step through it. Then in one of those classes I added a method that had some actual meaty logic.
It had the DebuggerStepThrough attribute on it, and I wondered about it for a moment, but then forgot about and coded away, making several copies of it to set up the classes that would provide the required XML structure.
The culprit? The attribute! I had copied a simple class used to represent an object that was serializable to XML. Using the Step Over command on the menu or by pressing F10 was causing it to step out of the method. All of a suddden, in one particular (new) file, I could not step using the debugger. On a side note, also make sure that you're in DEBUG mode, not release mode, when trying to use F10 to step over.Īnother very specific situation that could cause stepping to not work: I have been using VS for many years with no problem. 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. When I rebooted in "thawed" mode, the problems went away and I regained the ability to F10 normally. When it was in "frozen" mode, it was causing crashes, hangs, and strange and erratic behavior in other programs including Visual Studio. Unfortunately, Deep Freeze was protecting ALL of my hard drives, regardless of which drives I specified in the settings.
#CAMSTUDIO DISPLAY MENU SOFTWARE#
I was using software called Deep Freeze to protect certain partitions on my hard drive. SOLUTION: "Thaw" or uninstall Deep Freeze. When I tried to reset the shortcut key for the Debug.StepOver, it wouldn't accept F10 as input. The issue was the F10 shortcut simply was not working at all. My problem was caused by a very specific situation, so it might not work for everyone. 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. In the Add or Remove Programs dialog box, select Visual Studio then click Change/Remove. Please backup your settings before restore to default settings. Restores Visual Studio default settings by using "Devenv.exe /ResetSettings" command. If this feature works well before, and suddenly behave abnormally, it usually indicate that some files or configurations of Visual Studio installation is corrupted or missed, you can:
Second, to log all activity of Visual Studio to a log file for further troubleshooting, please use the /Log switch, and post the log file content here, so we can do more investigation on it. You can also try to run Visual Studio under safe mode, which will prevents all third-party VSPackages from loading when Visual Studio starts if the issue disappear under safe mode, you may consider checking your installed add-ons or VSPackages. In the Options.Keyboard page, please select "Debug.StepOver" from the command listbox, and then put focus to the "Press shortcut keys" textbox and press F10, click Assign button to re-assign shortcut, does it work?
0 kommentar(er)
