What IDE placement (output, errors, threads, watch, etc..) do you use (coding/debugging) in Visual Studio on Dual Monitors?
This is clearly subjective, but I keep my IDE on the primary monitor, right in front of me. The app runs on the secondary monitor, which in my case, is on the right.
hmmmm, I usually keep all IDE stuff in my larger left monitor, then the application in the right. More out of habit than anything else. Any suggestions?
minimal panes open (output sometimes), no animations, just a land of code and solution explorer all over my largest monitor.
When possible, I love me some portrait mode for writing code, my current monitors are landscape bound.
Editor windows on the big, primary monitor, and all my tool windows docked together in a maximized floating tool window on the second, smaller monitor.
The problem is that VS changes your layout depending on the current editor context; it changes on me when I debug, and I can never get it to stay exactly where I want it to.
Not long ago VS started throwing the tool window in the lower right hand corner of my primary monitor when debugging. I'm not sure exactly why the hell it started doing that, but I couldn't fix it. Had to give up and dock my tool windows when debugging.
HEY! Anybody know of a decent addin for controlling window layouts in VS?
Left: The IDE with as large an editor window as possible. Right: Everything else.
I always keep the IDE in the left monitor and save the right monitor for the app when running in debug mode. If you are setting breakpoints in message handlers for events that fire when a window is redrawn you can get into some irritating event loops when your IDE pops up and covers your app (likewise when you expose the app again).
Outside of that it really depends on which windows I need at the moment (call stack, output, memory, etc.).
We have some developers at our studio that use widescreen monitors turned vertical for more screen real-estate for their code. I think that you have to have driver support for this mode. For example, the nVidia control panel will support rotation of monitors to accomplish what I've described.
You lose the horizontal in favor of the vertical, but many programmers here really like that mode.
Properties window takes up 2/3 width of top half of monitor 2. Output/Error List/Pending Changes in a tab strip, ~100% of lower half of monitor 2. Everything else is on monitor 1.
I keep my IDE in my main monitor and put the properties, output, etc. tool windows grouped together detached on my secondary monitor. If I need to use the IDE and the secondary monitor at the same time (usually I don't, just because of the type of apps I've been working on currently) then I'll switch to having the tool windows re-docked and set to auto-hide (which also works pretty well when using remote desktop).
It depends on the monitors, I have my laptop on the left, due to the limitations of my desk, so I have got used to having my IDE on the decent monitor on the right.
I would say the IDE should be the monitor easier to see, my right monitor is more centered than the left laptop monitor
I use a Mac, therefore my Windows Vista (and XP) is virtualized in a VMWare or Parallels virtual machine. Both programs contain bugs when using multiple monitors and Unity/Coherence mode (that is, make the windows invisible and only see the running programs).
Only the latest VMWare 2.0 RC released a few days ago is capable of this. (not without some glitches).
I use a Macbook Pro and an external 22'' display. The "Main" display is the external (22 > 15) ;)
So the OS X menu bar, dock, etc. is there. The Macbook Pro internal display is the small secondary display, in my case, sitting left of the big screen.
When I use VStudio, I have the main VS display in the main display, maximized. And the Solution Explorer, Properties, Classes, and a few other toolbars, using the left smaller screen.
All I see is Code and some toolbars, but mainly all code.
When I debug, the floating tools disappear and others appear where the code is (the code window becomes a little bit smaller to accomodate this). No more floating stuff, as the application runs in the Macbook Pro smaller display, while I keep seeing the code/values/etc in the visual studio big screen.
It's a nice way to work. I'd recommend it anytime.
There are people that think that multiple displays not always means better productivity; solutions like "virtual desktops" are nice but cannot replace the speed of your eye moving from screen 1 to screen 2 to quickly glance at a property. I've tried Spaces on the mac and it doesn't come close. At least for programming.
I keep everything in the left monitor and my DB/Firefox in the right hand one.
Mainly because i switch dev between one monitor and two monitors depending where I am and I dont want to have to get used to two layout configurations for using VS.