.NET Tips and Tricks

Blog archive

Tool Windows, Begone

While all of the tool windows in Visual Studio (Solution Explorer, Properties, Debug) are wonderfully useful, the main editor/document window where your code lives is the one that matters.

You can instantly give yourself a document window that completely fills Visual Studio by selecting Auto Hide All from the Windows menu. This causes every (every!) tool window to turn into little labels hugging the borders of Visual Studio and popping out only when you want them (or when Visual Studio thinks you should want them). If you can't find Auto Hide All, it's because you've already closed or hidden your tool windows.

There is a downside to this: There's no "Restore to my last setting" option on the Windows menu so, you'll have to get used to having every (every!) tool window in autohide mode. You can get back to the default window layout for your configuration of Visual Studio by selecting Reset Window Layout from the Windows menu, but you won't get any customizations you've made to that setup.

There doesn't seem to be a way to save your favorite layout as the "default layout" that the reset menu choice restores. The only way to get back to your personal settings would be to have exported your settings at some point in the past and re-import them using the Tools | Import and Export Settings menu choice -- which seems like an awful lot of work (and not very speedy, either).


[Click on image for larger view.]
Figure 1. Big Editing Window. Auto Hide All opens up all the interior space inside the Visual Studio window for you to edit code.

But as I said, you get all of that editing space....

Do you have a Visual Studio tip you'd like to share? Send it to me at [email protected].

Posted by Peter Vogel on 03/22/2011


comments powered by Disqus

Featured

  • Full Stack Hands-On Development with .NET

    In the fast-paced realm of modern software development, proficiency across a full stack of technologies is not just beneficial, it's essential. Microsoft has an entire stack of open source development components in its .NET platform (formerly known as .NET Core) that can be used to build an end-to-end set of applications.

  • .NET-Centric Uno Platform Debuts 'Single Project' for 9 Targets

    "We've reduced the complexity of project files and eliminated the need for explicit NuGet package references, separate project libraries, or 'shared' projects."

  • Creating Reactive Applications in .NET

    In modern applications, data is being retrieved in asynchronous, real-time streams, as traditional pull requests where the clients asks for data from the server are becoming a thing of the past.

  • AI for GitHub Collaboration? Maybe Not So Much

    No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.

  • Visual Studio 2022 Getting VS Code 'Command Palette' Equivalent

    As any Visual Studio Code user knows, the editor's command palette is a powerful tool for getting things done quickly, without having to navigate through menus and dialogs. Now, we learn how an equivalent is coming for Microsoft's flagship Visual Studio IDE, invoked by the same familiar Ctrl+Shift+P keyboard shortcut.

Subscribe on YouTube