Should Visual Studio support dragging code files onto a secondary monitor?

I want to get a sense of how many people use Visual Studio with a mulit-monitor display.  I’ve seen some feedback in my blog comments requesting that we add a feature to drag a code file onto the secondary monitor.  Currently, in order to have source code on both monitors, you have to expand VS across the two monitors. 

  • Let me know if you use VS with Multi-Monitors.
  • Let me know if you want to have support dragging code files onto the secondary monitor.
  • Let me know if it came between having support for dragging code files onto secondary monitor and another feature, what would that other feature be?

I’m merely collecting this data as an experiement.  It’s kinda late in the game over here, so no promises.


Comments (103)
  1. YES!!! This would be huge! I’d love being able to look at multiple files from the same project in at the same time. I use my laptop monitor and a flat panel display for development most of the time, i frequently find myself flipping back & forth between code files in

    First Question: Yes

    Second Question: Yes

    Third Question: (disclaimer, this isn’t an original idea, i think i saw it somewhere {possibly even}) It would be very cool if the tabs for the open documents orded themselves in a last or most recently used order. For example I’ve got 23 open code files, it gets hard to manage/find my way around.


  2. David Levine says:

    I use dual monitors all the time. It would be extremely useful to be able to drag a file to the 2nd monitor without needing to expand the IDE to cover both monitors. In fact, I would almost kill (ok, perhaps just severely damage) to get this feature – call it the "severe damage" feature. Perphaps someone on your team could develop it in his garage to give it the proper killer feature feel.

    I usually separate the explorer-type displays (solution explorer, properties, etc.) so that they are displayed on the 2nd monitor and the source files on the main monitor, but that is usually because it is so difficult to get source files to display on the 2nd monitor without expanding the IDE. If it was easy to move source files between the monitors I would do it more often.

    A feature related to this would be to have a viewport memory mode so that I could create a custom view for the different display modes that was easy to recall. For example,

    VIEW1 = source files on main screen, explorer windows on the other.

    VIEW2 = source files on each monitor.

    VIEW3 = source files on main monitor, properties and solution explorer on 2nd.

    Present these on a menu so I could select one to quickly reconfigure the display.

    Another feature I’d like to see is to run compiles on a separate thread so that the UI is still responsive during a build.

  3. Sean says:


    The previous comments pretty much cover what I had to say 😉 But enhancing the multi-monitor experience should be a priority in Longhorn also..

  4. Nat says:

    Yes and yes. It should also support the code to be developed on one machine while testing it on another machine.

  5. LeeB says:

    I too find myself constantly flicking between source files in VS when ideally what I want to do is to place source files side-by-side. Editing multiple files using one monitor is cumbersome.

    I have dual displays and would love to drag a file to the second monitor for editing. Pretty much all the above applies!

  6. Don says:

    I can’t tell you how often I’ve wished I could tear an editor off onto another monitor…

  7. Eric says:

    Yes, yes, and I don’t know what the other options are.

    I often have multiple source files visible, and have currently resorted to having two code files visible on my main monitor either horz or vert, and all my dockable windows floating in a single "dockpane" of sorts… I make them all floating on my second desktop, then assemble them into a single structure.

    I would LOVE to have my help or other code file up on the second window EASILY.

  8. I’d like to drag text from the code editor and create little snippet files on a folder =)

  9. Sounds like it would be a great option, currently I have my monitors set up as:

    Left: Reference/Test Window

    Middle: Main code window

    Right: All my toolbars/panels/explorer windows.

    So I don’t know how often I would use that, but it would still be cool. What irks me, is if I stretch a window to span 2 monitors, and at some point lock the computer, when I come back and unlock it, the window has shrunk back to 1 monitor.

  10. Paul Holden says:

    I only recently acquired a second monitor at work and it’s taken me some time to adjust my working practices to take advantage of this. It’s amazing how used you get to having windows in certain locations when you’re working, and I’ve found it’s taken me some time to recondition my brain 🙂

    My current setup has the main window with code covering the whole of the primary monitor. The secondary monitor has the Solution/Class and Resource views sharing one toolwindow (taking up about 1/4 of the width on the left) with the rest of the space taken up with another toolwindow (with Output, Pending Checkins, Find Results etc etc). One of the reasons for this setup is that my secondary monitor is limited to 1280×768, so if I maximise an application, it won’t fill both displays fully.

    I’m not sure I would find having 2x code views particularly handy for day-to-day work. I think I’d find it quite hard to context switch across displays, but this is probably because I’m still getting used to having two screens. I have a tendancy to "lose" files even when they’re clearly visible in the tabs at the top of the screen, and having two code views might compound this 🙂

    What would be handy about having two code views:

    *) Side by side view of implementation/header files. I often use Alt-W,2 to swap between files I’m currently working on. Having the header open on the second display for reference/quick changes to declarations could be handy.

    *) Side by side view of Design/Code view for Forms etc.

    *) Being able to drag code between views on different screens could be very useful at times – e.g. when moving methods/fields when refactoring. Might well be quicker than cut/swap window/paste

    So for me, having the ability to drag code files to a secondary display isn’t a must-have feature, but that could be because I’m relatively new to the world of multi-monitors. Having said that, there’s all manner of snazzy features that you never really learn to appreciate until you’ve given them some time to get used to, so if there is time to implement this, I won’t be complaining 🙂

  11. Everything’s already been said here, but:

    Question 1: Yes!

    Question 2: Yes!

  12. rbishop says:

    another dual monitor user here. let’s see more apps start taking advantage of dual monitors properly!

  13. This would be a very nice feature to have… I have 3 monitors, and being able to pull code to one of the other two would be very handy

  14. Rick Preston says:

    That would be a great feature!

    I keep the code on my main monitor and the ‘extra’ IDE windows (explorers. output, search, blog reader, etc) on the secondary. I can’t say that I’ve needed it daily, but the times I’ve wanted it I’ve _really_ wanted it.

    So, to answer your questions:

    1. Yes.

    2. Yes.

    3. Autocorrection of other people’s bad code? I constantly get too many code windows open and accessing them via tabs gets clunky. Using the Window|Windows… menu is OK but it is a modal window. I have an add-in (in development) to get around this but it would be nicer to have out of the box.

  15. Sacha says:

    Hi Sarah,

    Each developer in our company (all five of us) uses a multi-monitor display.

    The ability to drag code files onto the secondary monitor would certainly be a welcome addition. To be honest though, this isn’t a make or break feature for us. I’d rather have a super stable feature limited visual than a sort of stable feature loaded visual

    I can see the ability to "drag-out" source files becoming more and more usefull as time goes on though. Especially as more and more of Microsoft’s tools get integrated into VS.NET (i.e. SQL Server Workbench, etc).

  16. David Cottrill says:

    I use a dual display daily for development, and I would enthusiastically welcome such a feature.

  17. There are 6 of us (5 dev + 1 photoshop guy) in our office that use multiple display. Applications that take advantage of multiple montors would help with productivity at times.

  18. Hi Sara,

    I’m quite addicted to using multiple monitors, so it would be amazing to see this feature 🙂

    The only ‘other feature’ I can imagine at the moment is the viewport-feature which David Levine suggested above… Seems like there should be something like this already in VS.NET since it distinguishes how the windows are arranged between coding/designing and debugging. For example to also have it distinguish between designing a Winforms form and coding would be great. Hm thinking about it it could of course be nice to have all the winforms-designing stuff at one monitor and the code for it at another monitor 😉

    If you can’t make it for Whidbey then I hope you put it very high up on the priority-list for Orcas!

    Rick Preston: Have you read Sara’s previous post? Seems there will come some new stuff which might help you with the problem in Whidbey…

  19. James Hancock says:

    ABSOLUTELY! What I would really like is to set the monitor that debugging happens on.

    It would also be great if you could put in a setting so that your code showed up on one monitor and your forms on another monitor so that you could see the form and edit the code at the same time!

    I couldn’t live without multi-mon while developing, it saves SO MUCH TIME! Please make more friendly!

    (I’ll trade Generics for Multi-mon!)

    I’ll trade partial classes for Edit and Continue in C# 🙂

  20. Absolutely. I use two monitors, and this feature would be a HUGE productivity enhancer.

  21. James Katic says:

    I have a different Multi-Monitor suggestion.

    I use VS with Multi-Monitors, stretched across 2 and sometimes 3 monitors horizontally. I use MDI mode (no tabs). When opening a new code window, the size of the new window is based on a percentage of the current height and width. This gets really irritating because that is always too wide and I have to resize each window after opening. I would propose that a new code window should always be contained within one monitors real estate.

  22. Mark Wan says:

    I have been using 2 monitors for over a year now. I like it so much that I have 2 monitors at home as well!

    Recently I have been reading code from multiple files and was trying to refactor them. One of my monitors is 21" and the other is 17". So expanding the IDE window to both monitors would not work. It would be really nice to drag a code window onto the second monitor and now you can cut and paste whatever you want.

    Another IDE feature that is nice to have is to set auto-indent for VB line continuation. Most of the time when we call a function we like to code it like this:, longVarName2, _

    longVarName3, etc)

    The C# IDE seems to be smarter but indents to about 1 tabstop behind the methodname. Not sure what other developers want but we seem to have the convention of continuing after the open parenthesis.

  23. Yes and Yes…. and for the 3rd question… nope, no VS feature I’d rather have 🙂

  24. Derek Price says:

    Absolutely. As it is, I have VW.NET on my main screen and NUnit GUI on my secondary (I’m not partial to the NUnit add-in). Any sort of improvement with this would be wonderful.

  25. Jason L. says:

    Absolutely! This would be a great boon for VS. Ideally, it would act such that a fileview could be drug out of the MDI on a primary screen to a secondary or tertiary………

  26. DotWind Blog says:

    This would be a very nice feature to have, I curently just use the screen splitter when I am dealing with long source files but that definetly is a good idea.

  27. Addy Santo says:

    Yes, Yes and Yes.

    I work with 3 main monitors (and another 2 laptops & a tablet), so the more support from VS – the better!

    More info at

  28. marko says:

    I’ll just be one of many to say YES! on all your questions.

    Multi monitor support definitely has made my development time and environment a lot smoother.

  29. Yes, No and n/a.

    I use two monitors for developing with Visual Studio: the main one is where I do all of my editing. The secondary one (on the right) is where I keep the MSDN Library , IE and RSS Bandit.

    I can see the attraction of being able to spread the files being edited between multiple monitors, but it’s not something I’m personally bothered about.

  30. Ryan Farley says:

    Hi Sara,

    Awesome idea. I would love to have dual monitor support in VS. I find that when a solution allows for multiple projects that I open each project separately (in two different instances of VS) so I can put them on seaprate monitors. However, when you’re working with two different items in the same project I’ve always wished I could open one code page on one monitor and another on a second monitor (or UI on one monitor and code on another) etc. For now it becomes a big pain flipping back and forth between the two code pages. I would love to be able to have that support built in so I could have it on both monitors and see it all side-by-side.


  31. Adam Hill says:

    1) Yes

    2) Yes

    3) I would be willing to give up improved Server Explorers or Copy Web imporvments.

    My big usage scenarios:

    – Help on another monitor

    – Code on another monitor (i use Web Matrix now)

    – Solution Explorer / Properies tab on another monitor (currently expand UI so the Solution Explorer and Props are on the second monitor)

  32. Todd Spatafore says:

    I too would like to see the multi-monitor support. I find that I can’t program anymore without at least two displays. As for what I’d give up to have it, well there are a lot of great features going into this release that I’m already sold on and I probably wouldn’t give up, so I could wait for Orcas to have true multi-monitor support, plus this would give your team the time to get it just right.

  33. sara ford says:

    Let me clarify one small point…

    For #3, i meant, "if it came between having two potential new features, like dragging code files to second monitor versus being able to maximize a tool window on the second montior", which of the two would you choose.

    Also, I know a lot of the time i want to maximize tool windows on the second montior. Let me know if you feel this way too.



  34. Yes, I’m a dual monitor addict. I feel naked and useless when I’m limited to only one monitor.

    Dragging files from the Solution Explorer in VS.NET out to anywhere on the desktop would be HUGE, HUGE, HUGE for me. I hate ctrl+tab’ing through my active tabs. Ideally, I’d like to be able to have VS.NET open but minimized with all of my code windows positioned (probably in a cascading fashion) on one monitor, with IE on my other monitor. I’d like to be able to build (or whatever VS.NET operations) while in one of my many code editors and not have a flicker from VS.NET or VS.NET restoring itself in front of everything I’m doing.

    Hrm, does that make any sense? 😛

    Thanks Sara! Great to hear you guys recognize the needs of us dualers!


  35. Sara wrote:

    Also, I know a lot of the time i want to maximize tool windows on the second montior. Let me know if you feel this way too.

    I do this all the time 🙂 It’s not very hard to implement it as an addon to Windows. Just create a windows service which is allowed to interact with the desktop and have it register a hotkey (I use ctrl+| as hotkey since it’s quite similar to alt+tab…). When you hit the shortcut the service should get the foreground window and if it’s not maximized then maximize it, otherwise move it over to the next monitor.

    Of course I’ve written such a service and if I had some time to fix some small bugs I would post it somewhere 🙂 But if you’re interested contact me and I’ll e-mail the source to you (just remove the obvious parts of the e-mail adress of the url for this comment…)

    I use the program daily and the bugs doesn’t cause any BSODs, but for example it doesn’t handle three monitors good 🙁

  36. John Cavnar-Johnson says:

    YES (Sorry for yelling, but that would be extremely useful)

  37. Dave says:

    Most deffinately!

    Yes, I use Multi Monitors

    Yes, I would love support for dragging source documents to the second monitor.

    I have recently gotten a second montor at work, unfortunately the second one isnt as large nad runs at a different resolution as the first one so spanning VS across both of them isnt really a good option. Right now I will commonly do one of the following.

    Left: VS full screen

    Right: Find results, chat windows,

    Left: VS Full screen with application being debugged on top of it, autos, locals

    Right: call stack, output window, breakpoints

    The last one I have tried doing is VS with document im editing on my left monitor and a second document I am referencing on my right monitor. My attempts to do this have included changing from Tabbed mode(my preference) to MDI and stretching VS across both monitors but IMO its a pain to do that, and then reset it to normal whenever you want. More often than not I just tab back and forth. I have also tried upening source files for reference in a plain text editor on the second monitor but this too is annoying, being able to drag documents from VS to the second monitor would be awesome.

  38. Ed Porter says:

    What I miss (from Delphi) is having the form on one monitor and the code on the other – save having to remember a lot of stuff.

  39. Steven Bone says:

    Let me add my yes to the pot. This feature alone would make the upgrade price of VS worth it!

  40. circuit_breaker says:

    I’ve got dual Sony LCDs, but don’t have Visual Studio. what’s that beta id for testing again? 😀

    cb <at> wasteland <dot> org

  41. Mikhail Arkhipov (MSFT) says:

    I am using two monitor and planning to get third one.

  42. Luke Foust says:

    I have been using a 3 monitor setup for a couple of years now. When I work in Visual Studio, I only have it span 2 monitors. Basically, I code on one screen, and have all the toolbars etc on the other. To answer your questions:

    1. Yes

    2. Yes

    3. Depends on the feature. The multi monitor coding would be pretty high on my list. But there are others above it.

  43. Philip Rieck says:

    1. Yes.

    2. Yes.

    3.Other feature: the ability to save/restore named sets of window layouts. For example, I have three monitors with toolbars / windows spread among the left and right, and the code in the middle. If I remote desktop into this machine (disabling the left and right monitors), or have VS up while disabling the left/right (with ultramon!), my window configuration is screwed up. I’d like to be able to keep the preferences and be able to switch amongst them. (I can make that easy enough with a macro, just make it possible!)


  44. I’m using only one 19′ monitor. May be because of this I don’t understand why do you need to spend resources to provide these features instead of something more important. Sorry to dissapoint you.

  45. pl says:

    2 more cents:

    I use a dual monitor setup for development constantly, but being able to open code on the second monitor isn’t a very high priority for me. The ability to maximize a tool window on the second monitor would be much, much bigger for me.

  46. AndrewSeven says:

    I only have one at the moment, but used 2 monitors for close to a year.

    The main thing I did was keep VS all alone on one, no alt-tabbing or other such ilk. It gave me a great feeling of continuity, never losing focus to read an email.

    The other monitor served for everything else : Outlook and other orifice apps.

  47. Kevin Moore says:

    I would love Multi-mon support in VS, but don’t limit it to just code files. As some have pointed out, the ability to move any window to the other monitor would be great. If I could move my watch + output window to my other monitor during debug I would be very happy.

    Supporting multi-mon in a generic way that supports all VS windows would be an amazing addition…

    [Disclaimer: My day job is work on the contact experience in Longhorn, but I do code at nights and on the weekends.]

  48. Anonymous says:

    Point of Origin &raquo; Multi-Monitor Support in Visual Studio

  49. anon says:

    I would like to be able to tile additional tool windows correctly in the second monitor and support for set-ups that have different resolutions on each monitor. This would allow me to dock tool windows correctly and reliably on the second low resolution monitor.

  50. Yes… Virtually my entire team uses multiple monitors. Please provide multiple monitor support in VS.NET.

    The only other feature more important would be method interception attributes. 🙂

  51. Absolutely YES to multi-monitor support!!!

  52. Yes, I love dual monitors. See My Current Hardware at I mostly work in Microsoft Access with the occasional VB utililty and some ASP.Net stuff.

    For Access work I’m thinking of doing what Allen Browne has done with LCD monitors. The left hand monitor is in standard landscape mode but the right hand monitor is in portrait mode. All the code goes on the right hand monitor. And now you can see a whole lot more code.

    And I can see using a third monitor down the road for help files, MSDN and other code searches, email, whatever.

  53. Sara,

    >> Let me know if you use VS with Multi-Monitors.

    yes. can’t imagine to develop with a single monitor.

    >> Let me know if you want to have support dragging code files onto the secondary monitor.

    thats not very important to me. i have online help, project view and stuff like that on the second monitor.

    >> Let me know if it came between having support for dragging code files onto secondary monitor and another feature, what would that other feature be?

    anything. don’t care about draggin code to the 2nd monitor.


    thomas woelfer

  54. Tero says:

    I use two monitors the same way most of the other commenters do: code on main window, toolbaars (solution expolerer, output, tasks etc) on the secondary display. After all those tool windows I have about 1/3 of the secondary display for other necessities like MSDN or Messenger.

    I don’t think I would often use secondary display for code editing or viewing, but it wouldn’t harm to have that kind of feature.

  55. MichaelM says:

    Yes & Yes.

    But _please_ keep in mind different resolutions. I run VS on my main monitor (1600×1200) so I can see at least a little bit more. The spanning two screens is just annoying.

  56. Alex Odintsov says:

    Yes, it will be very(!) useful. When you are working on a code, you are working with several files.

  57. Chris Bilson says:

    All .NET developers at my company automatically get dual monitors. Frankly, now that I’ve been using dual monitors for more than a year, I think any company that doesn’t just get every developer two monitors is stupid. Casual observation of a dual-monitor-virgin indicates to me that the extra monitor increases the developer’s producticity by 15-25%. That means we can recoup the cost of the monitor within a couple of days, and it’s just one more thing that makes developers feel liked in a company. We even tell people about our dual-monitor policy during interviews before our boss drops the bomb on them and tells them how little they will get paid. Some people still agree to come work for us. I bet it’s the dual monitors.

    I think the VS team should not only implement this feature, but take a look at other ways dual monitors could be taken advantage of to present more information to developers at one time.

  58. Yup, I use dual monitors with Visual Studio. For editing code I have one screen for code and one screen for floating windows. For debugging, I have Visual Studio on one screen and the app on the other. I am not so bothered about having two code windows because I haven’t needed that yet. The only extra feature I would like would be for tool windows to snap to each other and the screen edge when they are floating (so I can layout the floating windows on my second screen quickly).

    Also, if you could change the minimum requirements for Visual Studio to be at least 3 monitors that would help a lot when I try and convince people I need another monitor.


  59. I use dual monitors with VS.NET both at work and at home. I can’t live without it.

    1. Yes

    2. Yes

    3. Can’t think of any, so yah, that one would be great 🙂

  60. Adam Kinney says:

    I use dual monitors with VS.NET. I can’t live without it.

    1. Yes

    2. Yes

    3. number one in my book

  61. Paul says:

    Yeah, I’m one of those people that has to stretch the vs window across both monitors and put the files side by side. It’s pretty annoying, so being able to undock one of those windows would be awesome. Most of the time my second monitor is showing MSDN, but every now and again I want to use it that way.

    IN FACT, I would love it even more if I could look at different parts of the SAME file on both monitors; I use the horizontal split thing very often to look at different parts of the same file all the time, but you can’t see much by the time you split in half, plus toolbars, etc.

  62. Keith Wedinger says:

    I have a single 21" monitor so dual monitor support is not important to me.

  63. Evan says:


    What was the motivation behind not including this in the first place?

  64. Jason Nadal says:

    I do use vs on two monitors, and even tried to simulate having the aspx and the cs code behind on separate vertical tab groups; however, making a change on one vertical tab group doesn’t get refreshed in the other window (in my case, on screen 2) until it is clicked… I’d love for it to have live updates.

  65. KevMar says:



    Dual monitor setup is very adictive. I have had dual monitors at home for the longest time and have gotten some friends and family to adopt the idea. I finaly got it set up at work and another developer has done the same.

    One you have both, you hate to give it up. It changes the way you work.

  66. Kent Watson says:

    I think that it would be great to be able to create another Tab Group on a secondary monitor. Also I wish that XP would add a task bar to secondary monitors that has minimized window placeholders for applications running on that monitor. I downloaded a utility that does this but it is a little flaky.

  67. Page says:

    Yes, that would increase my productivity dramatically.

  68. Darron says:

    I’d love it. I wouldn’t trade my dual monitors for anything.

    Except, does anyone else see a shadow of the appearing between the two monitors after running the debugger? It’s a "white" window that covers the lower half of my secondary monitor. If you close that window, your VS window closes. VS is the only thing that does this on my machine.

  69. Mike Dunn says:

    Short answer: I would not put source files on a secondary monitor.

    Long answer:

    In my setup, my primary monitor is in front of me, and due so space limitations the secondary is about 70 degress to the right. When I’m in coding mode, I want everything on the primary monitor; I’m fast enough with the keyboard that Ctrl+Tabbing among source files isn’t a problem.

    When in debug mode (this is in VC 6 BTW, I don’t use VC 7) I float many of the debug windows to the secondary monitor. It’s the ones I want open but don’t look at too often – output (for trace messages). call stack, memory, and CPU registers. The source, watch, and variables windows stay on the primary since I look at those all the time.

  70. Sam says:

    I only use one monitor, the rest of the source I juggle in memory 🙂

  71. MATTHEW says:

    yes and yes

  72. Rich C says:

    I’m going to agree with the point that any VS window should be mobile on multiple monitors. I have three monitors running and will often open another instance of VS on monitor two to allow editing between files.

    I can’t imagine any of the VS sub-windows that wouldn’t benefit from the option to do this.

  73. William Luu says:

    Yes, most definately! Though, i’ve only just started using the multimonitor setup. But I can already see the benefits of working that way. And my job requires me to do more than just code, so dual monitors is definately quite useful (VPC running on one monitor, VS.NET in the other).

  74. NigWil says:

    Yes, dualing since late 1980’s (Macintosh II era)

    Yes please.

  75. Peter Evans says:





    What does it mean to my ALT-TAB ordering and-or ctrl-TAB ordering?,

    Does it apply only to source windows, what about other undocked windows.

    What about when I use full screen mode to see somebody’s spaghetti code more clearly can I get another source file on the other monitor full screen?

    Will it remember the source files position from session to session?


    Anything that is new special wizard templates stuff where I’m going to have to learn how it saves me time.

  76. Paulo says:

    Sure YES…

    I suposed that a multimonitor was a ‘must’ feature in this new release …

    Anyways, if you are going to implement it, keep in mind that, while tracing a program should be a option to choose which monitor the code and the running program appear. This way, you could "edit and continue" your code in one monitor and see the results in the other.

    keep it up !!!

  77. Yes


    Any tab should be able to be dragged to another screen

  78. Dan Golick says:

    Yes, I hate working at someone elses desk with only one monitor. I sometimes open another visual studio on the second monitor to edit/compare files.


    Better diffing tools would be a real help. (I love Beyond Compare)

  79. Jemm says:

    1) Yes, I use dual displays for developing at home and work.

    2) Yes, it would be really useful.

    3) Can’t think of anything right now, except the one mentioned earlier: code and form visible at the same time, like in Delphi.

  80. Mark Levison says:


    1) yes – I just wish I could find a third monitor.

    2) yes – it would save me firing up **jedit** on a regular basis.

  81. Tim Scarfe says:

    "Let me know if you use VS with Multi-Monitors."


    Let me know if you want to have support dragging code files onto the secondary monitor.

    Yes Yes Yes! Please I’ll do ANYTHING!

    Let me know if it came between having support for dragging code files onto secondary monitor and another feature, what would that other feature be?

    Realtime code visualisation in ORM, UML but also some 3d perspective visualisation similar to

  82. Howard says:

    I use a single monitor

    No opinion

    No opinion

  83. ShadowChaser says:

    >Should Visual Studio support dragging code files onto a secondary monitor?

    YES!! 🙂

    >Let me know if you use VS with Multi-Monitors.

    I can’t – current versions do not seem to support this! Theoretically "yes" – if it let me (properly)

    >Let me know if you want to have support dragging code files

    >onto the secondary monitor.


    >Let me know if it came between having support for dragging code files onto

    >secondary monitor and another feature, what would that other feature be?

    There is NO other feature I want more!

    I currently use two 19" LCDs, the primary in landscape mode and the secondary in document/portrait mode.

  84. Nicholas Stark says:

    Yes, I was just considering getting dual monitors because I heard how much it would help a programmer. I am just graduating and applying all over the place 🙂 Especially Microsoft.

    Anyways, i hooked up an old monitor to give it a shot and it doesn’t work well at all with dual monitors. I am kinda dissapointed but Visual Studio’s has been awesome so far I couldn’t live without it. So I guess I can let this slide 🙂

  85. Last year, I did a&amp;nbsp;very&amp;nbsp;informal survey on how many people out there use Visual Studio on Multi-Monitor…

  86. Matthew W. Jackson says:

    Everyone here uses a multi-monitor setup for developing.

    Those are good tips, but built-in support in VS would be nice. Two or more separate windows with their own set of documents and docks would be nice, with the ability to drag objects from one window to another.

    Or maybe get rid of all the nasty window hacks that make VS.NET a pain to use on Multiple monitors.

    The "fake" windows that show up half-way on the 2nd screen are annoying (I think it happens when the external help is open). Also, I can’t "Maximize to Desktop" with nView (part of the nVidia drivers) to automatically maximize across all monitors. VS.NET manually hooks the maximize event and ignores all attempts to maximize on both windows. I can’t even "Maximize to Grid," which is useful when running multiple instances of VS.NET.

    I don’t know why so many programs need to use these hacks and do their own thing. It makes customizing the window management in any way a big pain. VS isn’t as bad as Office, but the VS team seems to copy the Office team in a lot of ways, and this worries me. (What’s next? Each document will have an entry in the task bar?!?)

  87. Update 7/20 @ 9:20pm:&amp;nbsp; As i mentioned below in the comments, i think the best course of action is…

  88. Matthew W. Jackson says:

    I forgot to mention that my comments about nView were in regard to VS.NET 2003. I hadn’t tested VS.NET 2005 yet to see if it works with nView, and Beta 2 does indeed behave better.

    It’s a shame I can’t do all my development in VS.NET 2005.

  89. Update 7/20 @ 11:53pm: We have a bug:&amp;nbsp;&amp;nbsp;Please vote and leave your suggestions / feedback at…

  90. Update 7/20 @ 11:53pm: We have a bug:&amp;nbsp;&amp;nbsp;Please vote and leave your suggestions / feedback at…

  91. Bill Darcy says:

    >if you use VS with Multi-Monitors.


    >dragging code files onto the 2nd monitor.


    >what would that other feature be?

    why be bounded by an app’s rectangle? why can’t all VS windows be floating? code windows, data (output/varibles, …), toolbars, …

  92. Tom Scogland says:

    i would say yes to dragging code files to another monitor, but in all seriousness, i would be happy just having the tool windows able to maximize, that’s my only big problem with the multi-monitor support right now is that anything not on the primary monitor must be both manually resized and floating.

  93. Giancarlo says:

    I am actually using another editor on the secondary screen exactly because VS is (stupidly, I should say) missing this crucial feature. A Mac-oriented IDE, with a application toolbar separated from the tools and the editor windows would be ideal.

  94. dru says:

    +1000000000000000000000000 for Multi-Monitor Layouts

  95. YES!

    Using 15" laptop display and 19" TFT monitor. Now I am running VS in 19" display to get max working space. I am using laptops keyboard, and this forces me to work in non ergonomical position, writing to laptop keyboard and looking monitor in left side of me. If I only cound drag editor to laptop’s display and leave anything else to 19" display. Of course I cound get external keyboard, but it wastes table space and pushes laptop too far from 19" display.

    One text editor is enough for me, but I would be nice if I could use text editor on laptop display, and use form editor on 19" because 15" is too small for forms.

Comments are closed.

Skip to main content