Visual Studio 2008 and Multi-Monitor-Setups

Very recently my Visual Studio 2008 started to show some strange behaviour:
After moving docking / dockable tool windows to my second screen and arranging them there, I hit F5 to run/debug the application. This caused VS to crash and lose all IDE layout changes I had made so far. Reciprocally, changing the layout while debugging, then ending debug mode, results in the same error. I guess this must mean that the error arises when storing the IDE Layout for later retrieval. This behaviour is 100% reproducible.

The problem seems to be a well-known one in the Microsoft Development department, but no one seems eager enough to fix it, as a list of unresolved issues at Connect show (see here,here,here or here).

After Google did not provide me with a solution, I went on searching by myself, and the very first thing my Windows XP event log hinted me to was the failing component here, msenv.dll. Depending on your System, there are multiple flavours of that file installed (e.g. for VS2005, VS2008, Office11,...).

After some testing around (exchanging DLLs to ensure correct loading), I finally copied the version located at "/program files/commonfiles/microsoft shared/Help 9" to "$VS2008INSTALLDIR$/Common7/IDE", and finally can work properly again.

I draw the conclusion that my msenv.dll has been compromised, but how, by what and why?

What an ugly way of solving things...

Please note that I have posted this article before, on my private blog.

Kommentare

  1. Sebastian Edelmeier12. November 2009 um 02:25

    There's word out there that ReSharper is the one fiddling with msenv.dll, I will try to check this later on. I rather doubt it - If I recall correctly, I have tested this behaviour without ANY 3rd party component being installed on the system.

    AntwortenLöschen

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

WPF Diaries : Using HLSL pixel shaders

HLSL is mature language that enables developers to address the graphics hardware in a familiar, C-like way. Next to vertex shaders, you can use it to write pixel shaders, which is what - with .Net version 3.5 SP1 - Microsoft introduced into WPF. What sounds like no big deal at first sight is a major leap towards serius WPF / Silverlight game development and - more generally - graphically intensive UI. That goes hand in hand with the DirectX-powered concepts of WPF, finally giving .net developers a good deal of acceleration without the need for unsafe code. Since we're not doing heavy calculus on our GPU, even decent hardware is sufficient to display manipulated images. Since the death sentence of XNA , hopes were shallow that .Net developers get in touch with this cool technology, but we've always loved the walking dead, haven't we? Quite a few WPF Pixel Shader libraries and tutorials have popped up (Some are linked below), and I really recommend getting in touch with the
Mehr anzeigen

Getting the Crisp back into your WPF Apps

Bild
WPF has a lot of advantages, it's perfectly sane data binding mechanism being one of the most outstanding ones.On the flipside, many people (meaning companies, mostly) have refused to switch from WinForms to WPF because of the "blurry" looks of applications written in WPF. This blurryness goes back to two mechanisms: 1)Text Smoothing Instead of relying on the system's ClearType mechanism, WPF does it's own thing-a-magic, which is blatantly inferior to the aforesaid. In fact, WPF smoothed fonts are a definite way to headaches, if read for some time. Note : The image is from a website that compares various Microsoft.Net Font-Smoothing implementations. They might be useful to integrate text in images, though.For business applications (displaying data grids etc.) this is a K.O. criterion. Nobody wants to have to take their glasses off in order to achieve readability, and nobody wants their software deployed along with a pack of aspirins. 2)SubPix
Mehr anzeigen

WPF and Workflow Foundation : XAML parser compatibility issues

I am absolute and unrestricted proponent of the Windows Presentation Foundation , and I think I cannot say this often enough : It makes things easier and more structured. And I love it, somewhere close to every day. Now, as three quarters of this year have passed by without any significant smoke rising, I have also had the chance to get to grips with Workflow Foundation , and was literally astounded to see how far Microsoft has taken the idea of XAML (Yes, I'm a bit late to that party).  Combining the two technologies was the next obvious step, which worked fine until yesterday.  Here's the story:  In my somewhat completed WPF UI, I added a WF Activity. An instance of that Activity could not be created, Visual Studio kept throwing "Namespace or Type not found" like it was candy. Funny, though, that intellisense proposed both the class and the containing namespace of the Activity. A more complete description of the issue can be found in my StackOver
Mehr anzeigen