Apr 15

Written by: Euricom
4/15/2009 7:34 PM 

A few weeks ago, I started working on a new project for a customer. When setting up my development environment, I installed the PowerCommands add-in for Visual Studio. No problem so far, the installation went well, so I started Visual Studio 2008 and created a new project.

 

I added a new tab to the Visual Studio toolbox, I wanted to add some custom controls to this new tab by right clicking and choosing "Choose Items..." when all of a sudden ... Visual Studio just shut down! At first, I thought my laptop was getting really slow, but than I realised that Visual Studio had also disappeared from the windows taskbar. Strange, but not really a disaster. So I restarted Visual Studio and tried the same thing again ... with the same result too. The environment just kept crashing, and I didn't get a single error message telling me that something went wrong.

After a few more tries and some debugging, I opened up every developers favorite tool: www.google.com. The first search result took me to the Microsoft Support site at http://support.microsoft.com/kb/967679.

 

The cause for this crash appears to be a bug in the Common Language Runtime (CLR). In some cases, the System.Core assembly loses its native image and is loaded in the wrong context, which results in the crash. Adding a dependantAssembly element to the assemblyBinding element fixed the problem, as you can read at the MS support site.

Problem solved, now back to work! :)

 

By Kurt Torfs, .Net Solutions Architect

Tags: