VS.NET "dead" window

  • Thread starter Thread starter Brandon Potter
  • Start date Start date
B

Brandon Potter

Forgive me if this has already been covered...

I use dual displays and have 2 - 3 Visual Studio .NET 2003's open at the
same time, however, without fail, at some point during my session, the title
bar and border of one of the VS.NET's copies 1/2 of its height and 1/2 of
its width, so I end up with this floating titlebar and border taking up the
lower left corner of my 2nd monitor with an invalidated paint area.

Is there a fix?

Thanks,
Brandon
 
Chris Clark said:
I'm having the exact same problem. I posted a few days ago on
visualstudio.general, and haven't received any comments from MS. If
microsoft won't fix this in VS 2005 I'm going to be a little disgruntled.
There was a discussion around this earlier this year.

Here's what I heard from Microsoft:


Please let me know if you think that this applies:
Thanks,

John Eikanger
Microsoft Developer Support
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Hey Guys,

Thank you very much for bringing this to Microsoft's attention.

After looking at this thread, I found a bug which describes to be very
similar to what you guys are talking about.

Please let me know if you think following is the same behavior the issue
discussed here.

Description
==========
When using the Visual Studio.NET IDE on a dual monitor system, occasionally
the main application window will attempt to redaw on both displays.

Steps to reproduce problem:
(These steps may not always reproduce the problem)

* Open Visual Studio.NET.
* Move the window to the Secondary Display.
* Maximize the window.
* Open a project.
* Open a source file inside that project.
* Switch to another application in the Primary Display
* Click on the Visual Studio.NET IDE in the Secondary Display
* Attempt to click and drag to highlight some code.
* IDE becomes unresponsive.
* The IDE frame window is redrawn in the Primary display as well as still
existing in the Secondary display. However, the window in the Primary
display will have a solid white client area.

Note:
Program can be closed via the system menu button on either display.

Workaround:
When this happens, minimize both IDE windows. Then restore the window from
the taskbar. The IDE will resume it's position in the secondary display.

We are not able to reproduce this issue for next version of VS .Net.

Question
====
Are you able to reproduce the behavior on VS .Net 2002 or 2003 using above
steps?

Thanks,
Bhavik Shah
Microsoft Visual C++ Support
 
This happens to me too.

Chris Clark said:
I'm having the exact same problem. I posted a few days ago on
visualstudio.general, and haven't received any comments from MS. If
microsoft won't fix this in VS 2005 I'm going to be a little disgruntled.
 
Back
Top