Results 1 to 5 of 5

Thread: F11 not working as Step Into

  1. #1
    .NET Framework
    .NET 4.0
    Join Date
    May 2010
    Location
    Auckland, New Zealand
    Posts
    111
    Reputation
    108

    F11 not working as Step Into

    I have just set up a new laptop with the latest software including VS2017 (VS Community 2017, Version 15.8.8).

    From the VS Debug Menu, Step Into (F11) and Step Over (F10) work perfectly. However while pressing F10 works as Step Over, F11 doesn't but instead toggles Airplane Mode on/off.

    How do I change this so that, when I'm in VS, it works as Step Into?

    Thank you, Robert.

  2. #2
    .NET Framework
    .NET 4.0
    Join Date
    Aug 2004
    Location
    Sydney, Australia
    Posts
    14,001
    Reputation
    1730
    This has nothing to do with VS. VS isn't even seeing the keystroke because it's being intercepted by the hardware and/or OS. You would need to look into your system settings.

  3. #3
    .NET Framework
    .NET 4.0
    Join Date
    May 2010
    Location
    Auckland, New Zealand
    Posts
    111
    Reputation
    108
    John, this makes sense, but left me struggling to work out a strategy to fix the problem. A little more research and experimentation shows me that F10 is one of the few F-keys that hasn't an assigned function with this laptop. F2 appears to be the only other free F-key. For example F9 no longer toggles a checkpoint, but instead toggles the keyboard back-lighting. Then I found that everything worked as I wanted if the Fn key was held down, and I can lock the function key (on this keyboard with Fn-Shift, other keyboards may use Fn-Esc)

    Is there an easy way of turning Fn-lock on when VS starts? If not, well at least the problem is solved well enough.

    Thank you for your help.

  4. #4
    .NET Framework
    .NET 4.0
    Join Date
    Aug 2004
    Location
    Sydney, Australia
    Posts
    14,001
    Reputation
    1730
    That's the way with most laptops these days. You basically need to make a decision and stick with it: do you want to have to press the Fn key to activate hardware-specific functions or the standard function keys. The Fn key is not a standard part of Windows and would require interaction with hardware-specific drivers so you'd have to check your documentation for how to do that. I'd suggest that it's something that you need to train yourself to do but, to be frank, it's probably not something you should be changing anyway. On my Surface, I have it so that the hardware-specific functions are the default and the standard F keys require Fn to be depressed and I don't even think about it now. If you don't want things to be different on that laptop to a standard keyboard, do it the other way around.

  5. #5
    .NET Framework
    .NET 4.0
    Join Date
    May 2010
    Location
    Auckland, New Zealand
    Posts
    111
    Reputation
    108
    Yes, it's a bit of an adjustment. Everything has changed: I've gone from W7 to W10, Office 2003 to Office 2019, VS2014 to 2017, SSMS 2014 to 2017, plus all the 3rd party software (MicroFocus, Camtasia, WinZip, SmartFTP so far). So things don't work the way they used to, and it can take me quite a while to sort out how to do things that I used to know exactly what was needed. I'm getting there, and mostly I like the changes once I've figured them out, but if I could have migrated my old software as I migrated my data I would have done so and upgraded as I needed to. Pressing Fn is just one such adjustment, like you I'll soon stop thinking about it.

Similar Threads

  1. Question Debugging: Step Into (F8) Not Working
    By jcardana in forum IDE
    Replies: 3
    Last Post: 10-24-2017, 12:10 PM
  2. Replies: 0
    Last Post: 02-04-2015, 7:45 PM
  3. AxMediaPlayer Step function doesn't step backwards
    By pktechgirl in forum VB.NET General Discussion
    Replies: 1
    Last Post: 11-05-2011, 12:52 PM
  4. Visual Basic 2008 Step by Step book
    By albahith in forum General Learning Resources Discussion
    Replies: 0
    Last Post: 03-15-2008, 5:14 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •