Visual Studio 2008 with Dockable Tool Windows and Multi-Monitors. - by Adam Rieger

Status : 


Sign in
to vote
ID 376251 Comments
Status Active Workarounds
Type Bug Repros 5
Opened 10/17/2008 4:23:05 PM
Access Restriction Public


When docking multiple tool windows to each other and ending Debug mode or launching the IDE, Visual Studio 2008 will crash.

I use a mult-monitor setup where on the second monitor contains many tool windows (Task List, Bookmarks, Error List, Output, etc). In Debug mode, I have a whole new set of windows (Call Stack, Autos, Locals, Watches, etc). When all the tool windows are separate, to maximize space, each window has to be sized and placed and each window has a title bar. To get rid of the title bar on each window, I docked every tool window into one giant window with just one title bar. Docking all the windows together also helps with not having to reposition each one when system settings change which sometimes cause the windows to shift between both monitor displays. Docking works except the fact I cannot keep it this way as Visual Studio 2008 crashes when exiting debug mode or relaunching the IDE.
Sign in to post a comment.
Posted by Microsoft on 5/12/2009 at 5:44 PM
An updated hotfix has been released on the code gallery that addresses the xaml intellisense regression issue - please check out VS90SP1-KB960075-v2-x86.exe on It is not necessary to uninstall the v1 hotfix in order to apply this new hotfix. We're going to resolve this bug as fixed - please reactivate if you have additional issues.
VS Platform Shell Team
Posted by Microsoft on 4/15/2009 at 9:39 AM
Thanks for the additional information. We have been able to reproduce the problem and are currently investigating.
VS Platform Shell Team
Posted by Adam Rieger on 4/9/2009 at 9:51 AM
One more thing which I don't think will matter, I enabled the hidden guides feature in the Windows registry by adding Guides (REG_SZ) set to "RGB(255,0,0) 140", under HKCU\Software\Microsoft\VisualStudio\9.0\Text Editor.
Posted by Adam Rieger on 4/9/2009 at 9:46 AM
On both machines I installed DevExpress CodeRush Xpress 3.2.3, Divelements SandDock WPF 1.4.3 & SandRibbon WPF 1.1.2 and NUnit 2.4.8-net-2.0.
Posted by Microsoft on 4/8/2009 at 8:52 PM
Thanks for the additional information. Do you have any VS extensions or updates (e.g. Silverlight 3 Beta Tools) installed, or was this a clean VS 2008 + SP1 install on both machines? Reports of issues with this patch are rare so we're keen to narrow down what configuration results in this problem.
Visual Studio Platform Shell Team
Posted by Adam Rieger on 4/7/2009 at 11:01 AM
On both my machines intellisense stopped working after applying the patch however, on both machines I reinstalled SP1 and intellisense works again as well as the docking configuration that usually crashed the IDE.
Posted by Microsoft on 4/2/2009 at 8:26 PM
The fix captured in the patch is quite isolated to the IDE docking system, i.e. should not have impacted Intellisense. Are you seeing this on both your machines? Were there any other changes to the machine configuration that you can recall? Any further information you have that could help us track this down would be appreciated.
Visual Studio Platform Shell Team
Posted by Microsoft on 3/26/2009 at 9:32 AM
Thanks for letting us know, we'll take a look at that...
Posted by Adam Rieger on 3/19/2009 at 2:40 PM
After a couple of days from patching, I've noticed that my intellisense for WPF XAML no longer works. Instead of the intellisense popups when typing a first character, I get 2 errors immediately:
553 Expected '='.
554 Expected an attribute value. Attribute values are delimited by a single quotation mark (') or a double quotation mark (").
Now I don't recall these errors popping up almost instantly after typing a first character.
Posted by Adam Rieger on 3/18/2009 at 12:03 PM
Patched VS and no crashes so far on two different layouts (work & home pc).
Posted by Microsoft on 3/17/2009 at 9:03 PM
In addition to making sure this issue is addressed in VS 2010, we have been pursuing producing a patch for VS 2008 SP1 to resolve this issue. This has been released on the code gallery - please see: If you find the patch does not resolve this problem, please reactivate with details.
Visual Studio Platform Shell Team
Posted by S. Edelmeier on 3/6/2009 at 1:09 AM
what i meant was msenv.dll
Posted by S. Edelmeier on 3/6/2009 at 1:05 AM
I just copied the dll from "%shared%\Microsoft Shared\Help 9" to the "%VSINSTALLDIR%\Common7\IDE" folder and it works like a charm.
Don't know why, but the suspicion that VS writes into that DLL creeps up on me : the faulty dll was 9138KB, the one that works is 9136KB.

This works fine for me, hope it will help you as well.
Posted by Adam Rieger on 10/29/2008 at 1:19 PM
When you say next release of Visual Studio do you mean 2009 version or SP2 for 2008?
Posted by Microsoft on 10/28/2008 at 6:01 PM
Thanks for reporting this issue. We have reproduced the problem and will address it in the next release of Visual Studio.

Visual Studio Platform Shell Team
Posted by Microsoft on 10/20/2008 at 9:44 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(