I have two computers at home. Both have Visual Studio 2013 with power productivity tools extension. The only difference is one computer has windows 7 while another is running windows 8.1.
Both are running same edition of visual studio and latest updates are installed. But on windows 8.1 machine pressing Ctrl + Shift + Enter does not put semicolon while with windows 7 it's working fine.
Can anyone please tell me is that OS specific problem or there is a bug in power productivity tools for visual studio 2013.
reference: http://abhijitjana.net/2010/07/21/use-shiftenter-to-add-automatically-at-end-of-the-line-visual-studio-2010-productivity-power-tool/ - This link is for visual studio 2010 but now visual studio 2013 got same functionality with Ctrl + Shift + Enter.
Just tested it on mine (VS2013 w/Power Tools) in a C# file on windows 8.1 and it worked.
My recommendation is that you verify that the mapping (Edit.LineOpenBelow) is mapped to the keystroke.
Do you have other tools which may have taken the mapping such as Resharper?
If the mapping is there and appears to be assigned, try to change the mapping and see if it it works or fails. The mapping can be found in the keyboard options here:
Apparently in Windows 8 (and Windows 8.1) a special shortcut was added to run a task without showing the UAC notification to grant administrator privileges when running a specific application.
Surprisingly the shortcut is Ctrl + Shift + Enter.
Source: http://www.tekrevue.com/tip/command-prompt-administrator-shortcut/
So the question is how to disable it and if it will solve your issue:
You can disable the sequence Ctrl + Shift in Windows 8.
In "Control Panel" | "Clock, Language and Region" | "Language" click "Advanced Settings" in the left pane.
In "Advanced settings" click "Change Language bar hot keys"
In "Text Services and Input Languages" click "Change Key Sequence" button and disable the the key sequence by selecting the "Not
Assigned" radio buttons.
Source: https://superuser.com/questions/604790/how-to-disable-ctrlshift-keyboard-layout-switch-in-windows-8
Or you can try to disable the UAC:
Open up the Start screen, search for UAC, and you should see an option
for User Account Control settings. If you don’t, you’ll need to change
to search through your Settings first, but then you should see it.
And then you can drag the slider all the way to the bottom, the same
as for the other versions of Windows.
Source: http://www.howtogeek.com/howto/windows-vista/disable-user-account-control-uac-the-easy-way-on-windows-vista/
You can also try using SharpKeys to redefine the specific keyboard sequence:
Download link: http://www.randyrants.com/2011/12/sharpkeys_35/
Guide: http://www.askvg.com/customize-any-key-in-your-keyboard-using-sharpkeys/
Now, after doing it, please try the hotkey in VS2013.
Let me know if that support your issue,
Related
My quick watch (shift + F9) shortcut suddenly is not working.
But its alternate keyboard chord Control + Alt + Q works fine.
And all other shortcut seems working fine. But quick watch is the only one that I currently found.
I have tried other shortcut with Shift or with F9 , no problem.
I am also using Resharper, is that affecting VS Shift F9?
If you have Snag-It installed on your machine, its global shortcuts may override application specific shortcuts in Visual Studio (or other apps).
See #nuri's answer here: Visual Studio 2010 QuickWatch window not visible for instructions and screen-shots to change the Snag-It settings.
In the meantime, just go into the Snag-It preferences, the HotKeys tab, and set the "Video capture start/pause/resume" hot key to something other than [Shift]-[F9]. For myself, I only use "Global capture", so I set everything else to "None".
You can try the following:
In TOOLS --> Options | Keyboard, make sure the right mapping scheme is selected (Visual C# 2005 for me) and click Reset and finally, Ok
I just got a new computer with Windows 8 and installed Visual Studio 2013 on it and now I have an issue with debugger shortcuts - I run application in a debug mode and it breaks at the first break point but when I try going further line by line, F10 does not work from the keyboard - only VS Debug menu. Anything I am missing?
P.S. The issue was the function key. It needs to be turned on in order to use F keys
On Lenovo laptops, there is a shortcut to disable the Fn key automatically running the default Windows shortcuts.
Hit the Fn key and the Esc key at the same time to toggle the "Hot Key" default.
Hope this works for other Laptop brands since this is an easy shortcut for newer Lenovo laptops.
Please follow the instruction here, though it talks about visual studio 2010 it should help you to analyze the problem. it may be solved with the steps described there and if not, please let me know...
Why does F10 (step over) in Visual Studio 2010 not work?
Update Adding the answer from the source in case the link will be removed:
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?
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.
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.
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:
Restores Visual Studio default settings by using "Devenv.exe
/ResetSettings" command. Please backup your settings before restore to
default settings.
Repair/reinstall Visual Studio;
To repair Visual Studio In the Add or Remove Programs dialog box,
select Visual Studio then click Change/Remove.
I resolved my issue and wanted to post an answer in case anyone is looking for it. Enabling function key does not require any complicated solution, it can be enabled by changing settings in:
Control Panel -> Hardware and Sound (Category) -> Windows Mobility Center -> Adjust Commonly Used Mobility Settings
Look Under Function Key Behavior and change the dropdown value to "Function Key" to enable Fn key.
To disable it, select "Multimedia Key"
See: http://elena-sqldba.blogspot.com/2015/05/how-to-enable-function-key-on-windows.html
Also check 3rd party software. In my case I had Camtasia Recorder open and minimized, which apparently intercepts the F10 input (thanks, TechSmith)
I had the same problem. My solution was a bit different and can apply to any key. My F10 key was not working. After unplugging the keyboard and plugging it back in did not fix the problem, I twisted the keyboard like an ice cube tray and the F10 key started working again.
I can't use Ctrl+, in Visual Studio 2013 and Pycharm in windows 8.1. Is there a way to find which application occupy this shortcut/hotkey?
I tried Windows Hotkey Explorer, doesn't work.
Here is the list.
Here is the list of the program I installed:
Any help?
This is for Chinese user only. This is because of the Sogou Pinyin (搜狗输入法）occupy this shortcut system wide. And it won't release if you just uninstall it.
Go to here to disable it: Language->Advanced settings->Change language bar hot keys
Uninstall it is not working, you need disable that setting then uninstall it.
Adding to #happlebao's answer:
As of 2019, in Windows 10, you need to go to Settings > Devices > Typing > Advanced keyboard settings > Input language hot keys, or just press Windows key and search for "Advanced keyboard settings" to find the hotkey settings.
Then disable the Ctrl+, hotkey.
I'm testing visual studio in desktop parallels win7 running on my Macbook air. Everything works fine except that i cannot get curly braces to work inside visual studio.
The Curly braces do work Shift + right-alt 7/8 (tested in notepad) but something is overriding the key combination inside visual studio.
software specs in parallels
Windows 7
Visual studio 2012
Resharper
I think it is Resharper that is messing with me. Does anyone know how to turn off a shortcut, specifically the key combination shift + right-alt + 7/8 so i can get curly braces working again.
You can check all the different shortcuts in Visual Studio and modify them as you like.
In Visual Studio goto: Tools -> Customize and press the Keyboard button at the bottom.
Then, in the "Press Shortcut Key" TextBox just press the key combination and you'll see what command it is set to, and you can remove/redefine that combination
I had the same problem, but I finally found how it work:
for { type right-alt+5 and for [ type right-alt+shift+5
In Visual Studio 2015 the keyboard settings are at Tools -> Options under Environment/Keyboard.
I could not find the bound command by pressing the shortcut.
After some digging i discovered the command name: ReSharper_EnableDaemon. Removing all shortcuts for this command, I can now type { again.
Try to use fn + alt (right alt key) + 7/8 in your keyboard. Should fix most of those Mac parallel issues.
I am trying to learn the keyboard shortcuts in Visual Studio in order to be more productive. So I downloaded a document showing many of the default keybindings in Visual Basic when using the VS 2008 IDE from Microsoft.
When I tried what they say is the keyboard shortcut to view all open documents (CTRL + ALT + DOWN ARROW), I got a completely unexpected result on my XP machine; my entire screen display was flipped upside down!
Was this a prank by someone at Microsoft? I can't imagine what practical value this flipping of the screen would have.
Does anyone know what the correct keyboard shortcut is to view all open documents in VS 2008?
Oh and if you try the above shortcut and it flips your display the way it did mine, do a CTRL + ALT + UP ARROW to switch it back.
This is a conflict between your graphics driver and Visual Studio. Go to your driver settings page (Control panel) and disable the display rotation shortcuts. With this conflict removed, the shortcut will work in Visual Studio.