Visual Studio and dual/multiple monitors: how do I get optimized use out of my monitors? [closed]

Answer 1

Three monitors -- all 1600x1200

• Left: Email, IM, SQL Server Management Studio, Remote Desktops to servers
• Middle: VisualStudio -- maybe multiple instances -- maximized, solution explorer and team explorer docked on right, errors/output docked bottom, others auto-hide
• Right: Web browsers -- app debugging and normal web work, ADUC (if needed)

Other apps get moved around depending on what I'm working on and how crowded the monitors are and the interaction between the app that's open and what I need the info from it for.

Answer 2

When I first got two monitors I wanted to do the same as you, use all the space for visual studio, but I think that you come to realize that it's best to keep VS on one monitor and use the second monitor for documentation, external resources etc. You wouldn't think it at first, but all the little touches like just being able to maximize other resources without them hiding your code is a great feature.

Answer 3

Though I use StudioTools for other purposes, it has a "Tear off Editor" option, with which you can "tear off" the file to a window and resize the window. Find it quite helpful

Answer 4

I find the Code Definition window absolutely invaluable to have open in my other monitor. As the cursor moves over a type name in your editor the other window shows its definition.

Answer 5

I have three monitors, set up where Visual Studio is full screen on the middle monitor, the right hand monitor has all the tool windows configured and the left monitor is for browser, help, SSMS, email, etc..

Works well except if I have to remote in, so I have a separate exported configuration to bring move the tool windows back into Visual Studio, and one to set them back up for multiple monitors.

Answer 6

For GUI debugging is awesome being able to run the app into one screen and having the debugger in another screen. That's one of the most practical uses..

But really, depends on which kind of application you're developing, i.e., if you need to monitor open file handles, logs, etc.