Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Visual Studio 2013: Window.PreviousTab changes design/split/source views instead of tabs

In Visual Studio 2013 Professional, the keyboard shortcut which is supposed to toggle to the previous tab, bound through Window.PreviousTab, seems to be toggling the Design/Split/Source views:
Design | Split | Source

I went ahead and tried to isolate the problem by removing everything connected to the default keybindings of CtrlPage Down and CtrlAltPage Down. I also completely removed all keybindings for Window.PreviousTab and Window.NextTab so that nothing changes the windows.

I then bound CtrlTab to Window.NextTab and it worked fine for going to the next tab. Then I removed that and bound CtrlShiftTab to Window.PreviousTab and it toggled the Design/Split/Source view instead of the tab. I removed that and bound it to CtrlTab and it had the same effect. There are no other bindings using CtrlTab or CtrlShiftTab.

What is causing this, and how can I fix the problem? Is it a bug?

The only extension I have is PHP Tools for Visual Studio.

like image 460
Keavon Avatar asked Jan 26 '14 20:01

Keavon


People also ask

Does Visual Studio use Tabs or spaces?

This is the Adaptive Formatting behavior in Visual Studio: the Editor heuristically determines if the current file should use Tabs or Spaces for indentation. To turn off this behavior, please go to Tools > Options, and then Text Editor > Advanced > Uncheck "Use adaptive formatting".

How to Adjust windows in Visual Studio?

It's easy to set your default layout: Arrange your windows the way you like, go to the Window menu in Visual Studio and pick Apply Window Layout > My Default. If you want you can setup several window layouts by picking Window > Save Window Layout. This choice gives you the option of assigning a name to your layout.

How do I make multiple Tabs in Visual Studio?

For those using Visual Studio 2022, check the "Show tabs in multiple rows" setting in Tools > Options > Environment > Tabs and Windows section. Save this answer.


1 Answers

I had to look for it for a while, this was intentionally removed. For a good reason, this is legacy. It didn't get any love at VS2010, just the minimum to still make it functional, WebForms is not Microsoft's priority. Very high odds that you can't fix this and the keybinding was hard-coded in the extension.

But don't take bad news from an SO user, nobody ever likes that, get it from horse's mouth. Also a basic way they find out what their customers care about. Post the issue at connect.microsoft.com

like image 147
Hans Passant Avatar answered Oct 23 '22 11:10

Hans Passant