In SQL Server 2012, Ctrl+R not working. Any other shortcuts for that.
Any setting changes available or is there any alternative?
Go to Tools > Options > Environment > Keyboard / General.
In the middle box,
Select Window.ShowResultsPane
Change the Use new shortcut dropdown to SQL Query Editor (Global did not work for me)
Put your cursor in the "Press shortcut keys:" box and hit CTRL + R. You should see the following:
Click Assign and then OK.
Unlike some other changes that still require an SSMS restart to take effect, the change takes effect immediately, and CTRL + R should start working again.
I blogged about this three years ago.
Another way is to select Default and hit the Reset button. This worked for me.
I'm using Microsoft SQL Server Management Studio version 11.0.3128.0 (SSMS 2012).
Started having the above issue for no aparent reason.
Solved like this: click "Tools -> Options". On the options window, open Environment -> Keyboard on the tree. Then, on the right, press the "Reset" button.
Worked for me.
I am using Microsoft SQL Server Management Studio version 12.0.4100.1 (SSMS 2014).
I had the same issue and resolved it by following below steps -
Click "Tools -> Options".
On the Options window, expand Environment -> Keyboard -> Keyboard.
Then, in the right side panel, press the "Reset" button.
Go to the Keyboard Settings as mentioned by #aaron and then change the keyboard mapping scheme (first drop down). This gave me back the shortcuts that I am used to like Ctrl+R and Ctrl+E
I am troubled with this after I installed Visual Studio 2015. When Ctrl+N is pressed in SSMS, instead of opening a query window, SSMS showed up selection page of the VS files. A Reset as posted above revert to SSMS shortcuts.
Thanks for the posts.
--In 'thoughts'...
I just upgraded my Visual Studio from 2012 to 2013 and haven't done anything else yet short of installing all the updates recommended.
For whatever reason, when I go into my solution and press F10 or F11, it runs the entire program as if I had pressed F5... F8 works the way F10 used to, but I don't know why the keys I've always used now don't.
I set up visual studio as a VB environment.
How can I fix this?
Thanks!!!
Additional Info:
Just to add on as much information as I can, if I set a breakpoint in my code, then I can use F10 / F11 to continue stepping through my code once the breakpoint is hit and execution is stopped as would be expected.
EDIT 2013-12-31:
Based upon a comment made by Neolisk, it appears this is simply a change in default behavior in Visual Studio 2013... If anyone knows how to change this back to the way it was in 2012, that would be GREATLY appreciated, but at least I now know it's not an error / installation issue.
If 2013 works the same as previous versions, then do the following:
Navigate to Tools > Import and Export Settings
Choose "Import selected environment settings"
On the next screen, choose to save your current setings if you want to.
When you get to the point where you can import, just select "General Development Settings"
That should set everything back to what you're probably used to. Most people are set up using general settings and either don't realize it or just forget.
EDIT: If your issue is that the program executes when you press F10 or F11 when you are not debugging, then I think you might be out of luck. It's done that to me personally since VS 2008 (I'll frequently miss the F12 key when I'm in a hurry), and, after some searching, I think it actually happens to everyone:
Visual Studio - Prevent F11 from starting the debugger?
My guess is that this is a side-effect of not being able to set contextual hot keys based on whether you are or are not debugging. Since F10 and F11 are tied to debug-execution-related operations, my guess is that Visual Studio realizes that it needs to be debugging to process them, and thus starts the program.
ANOTHER EDIT: Of course, it's also possible that you had the scheme set to something else entirely in VS2012. Check out all of Visual Studio's pre-defined hotkeys by environment here: http://msdn.microsoft.com/en-us/library/da5kh0wa(v=vs.120).aspx
If none of those have the mappings that you're used to for F8, F10, or F11, then it's possible that you or an add-on may have had few custom hotkeys defined.
Worst-case scenario, you can simply redefine your shortcuts manually by key in the keyboard settings: Tools > Options > Environment > Keyboard
It sounds like you are in VB settings and not C#. You should try changing your settings to one or the other and see if those debug options change. On my machine
Tools - Import Export Settings - Reset All Settings - C# (If you want F10/F11) VB if you want F8/Shift-F8. It doesn't matter what your settings are you can still code in both languages, but if you are used to pressing F10 to debug VB.NET code you've been using C# settings this whole time. Nothing new with Visual Studio in this regard. I am using VS2013 Ultimate, have been using Visual Studio since VS2003.
The first image is VB.net, second is C# settings
You can try some of these reset settings:
And different combinations thereof, i.e. ResetToBasic first. If does not help, try ResetToC#, then back to Basic. Then try General, back to Basic. See if you can hack your way through like this.
EDIT: I tried my VS 2012, and compared to VS 2013. What you described is completely normal. VS 2012 used to step in Form_Load and similar on F10 and F11, VS 2013 no longer does it. So it seems like your VS 2013 is working as expected.
Microsoft probably has a reason to not allow to step into a property by default.
Properties are supposed to be mostly get and set and not contain a whole lot of implementation in it. But that may not be the case all the time.
If somebody is trying to step into a property that means this developer is suspecting something in that property that may be causing problems. So by default this behavior needs to be reversed and allow stepping into properties.
For now this is how you can enable stepping into properties.
Go to Tools > Options menu in Visual Studio.
Goto Debugging > General menu item in left pane.
In right view you will see and option Step over properties and operators (Managed only). Uncheck this option and then you are all set.
Enable step into properties in Visual Studio Debugger
If the above didn't work then follow this
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 found I had to run VS as Administrator to debug properly. I also do a clean solution prior to debugging, especially on x64 machines. If you put a manual debug breakpoint in the code and the IDE indicates it can't stop at that point, then it's possible that the debugger is out of sync with the source code.
An idea to test it in a short way:
Create a Hello World console app.
1 Module Module1
2
3 Sub Main()
4 Console.WriteLine("Hello")
5 End Sub
6
7 End Module
Build first.
Put the cursor in line 4 (before each step), commands should start Debug Mode if you are in Design Mode.
F10 (StepOver): Should break on line 3
F11 (StepInto): Should break on line 3
CTRL+F10 (RunToCursor): Should break on line 4
If it is working properly: Maybe the assembly which containing the entry point of your program had modified and wasn't been rebuilded, or there is somthing other problem with the point where the control expected to break.
If it doesn't work as expected on the sample, I think you should ask on MSDN FORUM or make a bug report.
I don't know why they might have intent to change this behavior.
It is working for me in my 2013 Express Edition with C# recently.
I found what I think is an acceptable workaround for the non-functioning F10/F11 Keys. They are probably the most used keys in stepping through code, and it is a real pain to click on debug and select the key from the dropdown.
I got around this shortcoming by adding icons to the toolbar for these operations.
If you are not sure how to do this, On the Debug toolbar click on the down pointing arrow near the right side of the bar. Click on Add or remove buttons.
Select Customize...
Select Add Command
Select Debug
Scroll down to the desired key (Step over / Step into)
You once clicked, you will see the two icons added at the left side
of the toolbar, Unfortunately they are the same Icon, but with a
little use, you should be able to select the right key to click on.
I actually prefer this method to trying to remember which function key
to press.
On many branded laptops, there is an extra button "Fn", Press "Fn" and "Esc" together. Functional keys will be enabled in visual studio.
Kindly press Fn key and Esc (with Lock with Fn label).
Sometimes it gets locked and Media Player buttons get activated.
Sounds stupid to ask but what type of keyboard do you have? I know some keyboards have different modes that allow you to set different profiles for keys based upon the application. I use the feature with my Microsoft Natural keyboard. However I have had problems with the profile still being active when I switch into Visual Studio and then F10, etc doesn't work correctly.
I faced the problem that F10/F11 doesn't work but the breakpoint works.
Once I uninstall the Security Software and unload the relevant drives it works again.
So my advice is that. And I guess it's due to the drives, so if these don't work just try to unload those questionable drives may connected with this question.
Using Logitech MX 3000 Keyboard, I've upgraded to the last setpoint version and these keys work now perfectly. (Driver version 5.90.41)
I would be delighted, elated even, if someone could tell me how to close every tool window in Visual Studio 2013 in an automatable fasion. Solution Explorer, Output Window, and Toolbox are all examples of the countless tool windows that can accumulate on my screen. I'm using Autohotkey to try to close them, but it has become impossible to do through blind keyboard shortcuts (AFIK.)
I'm not opposed to a plugin but something with just the keyboard would be ideal.
Thanks so much!
If you want to do it with Autohotkey, take a look at WinClose as MCL suggested. You might also need SetTitleMatchMode.
I'm still using Visual Studio 2010, but with some minor adjustments it should also work in Visual Studio 2012:
SetTitleMatchMode, 2 ;No need to enter the full title
Enter:: ;press enter to close all tool windows
WinClose, Microsoft Visual, Find and Replace
WinClose, Microsoft Visual, Solution Explorer
WinClose, Microsoft Visual, Class View
WinClose, Microsoft Visual, Property Manager
;...
Sleep, 1000
Return
Esc:: ;Use Esc to exit the script
ExitApp
Use "AU3_Spy.exe" form your Autohotkey folder to find the WinTitle(part) and some visible text.
Layouts-O-Rama is my take on the problem. To be found in the vs gallery here:
http://visualstudiogallery.msdn.microsoft.com/35966ad9-430f-4ad7-9186-4394b784e36c
Basically the addin saves tool window layouts. You could simply save a layout with all tool windows closed and assign a hotkey to it. To go even further you could save another layout with all the tool windows you like opened and assign a different hotkey to this.
I haven't been able to find anything that can colour the background and/or add a tab bar to the SMMS IDE to better identify the difference between prod, test and dev servers. SMSS Tools appears to be the only plugin trying to do this but I'm yet to see it work (appears to be a common problem based on my searches).
Just wondering if anybody knows of an addon (paid or free) that accomplishes this?
All version of SSMS since at least SQL Server 2008 R2 (and I think 2008) include a built-in ability to change the colour of the connection bar at the bottom of a query window - when setting up a new connection for a query, click the Options >> button, then set the colour by ticking use custom colour (then selecting your chosen colour) on the Connection Properties tab.
I've had SSMS Tools Pack connection colouring working but I prefer the built-in option.
EDIT
I just tried SSMS Tools pack colouring again, and I agree it appears not to be working in the current verion (2.1.0) in SSMS 2008 R2.
I'm looking to create a shortcut to change the connection of a query in SSMS. Is there a way to manually assign shortcut keys to buttons?
Look in Tools - Options - Keyboard.
See also this.
SSMS Tools Pack Snippets is the nearest I can find to highly customisable keyboard shortcuts/hotkeys. For SQL 2012 on it's no longer free. The options mentioned above (unless I'm missing something obvious) don't seem to allow you to set your own shortcuts. There are twelve keyboard shortcuts listed (from Alt+F1 to Ctrl+0) but for the life of me I can't work out how you can add your own to this list.