Visual Studio 2008 – PowerCommands Woes

Today Visual Studio 2008 started crashing every time I attempted to open a specific XAML file. Ungracefully, the IDE shut down without warning, again and again and again…

Checking the event viewer I found the following error message:

The remote debugger is unable to communicate with Visual Studio, and must abort the remote debugging session. Please restart debugging.

The only recent update to my configuration is the installation of PowerCommands (link), an extremely useful toolkit that boosts (my) productivity by adding some additional commands to the IDE (other than this bug, it is definitely something I recommend checking out).

With this error message and hunch in hand, I set out to find the root of the problem and came across the following discussion on MSDN (discussion link), providing the following solution:

Using notepad (with elevated permissions in Vista/Windows 7) open the devenve.exe.config file in the path appropriate to your installation:

  • C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE – x86 path
  • C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE – x64 path

Add the following code to the assemblyBinding section of the config file:

<dependentAssembly>
   <assemblyIdentity name="Microsoft.PowerCommands" publicKeyToken="null" culture="neutral"/>
   <codeBase version="1.1.0.0" href="C:\Program Files (x86)\PowerCommands\Microsoft.PowerCommands.dll"/>
</dependentAssembly>


This solved my (and, if you got here from google, hopefully your) problem!

Comments

John Croasdale said…
Worked for me too. Thanks for sharing!
If you ever find yourself in Nottingham (UK) I owe you a pint :-)

And here is me cursing the JetBrains addins that I recently installed, I forgot about the powertools I installed the other week. Oops! Sorry JetBrains
July 14, 2010 at 6:23 AM
Post a Comment

Popular posts from this blog

Excel - Adding an existing Pivot table to the data model

Image
  I've been working more with, and continue to be amazed by, Power Pivot. I recently ran into an issue where I needed to add the data for an existing Power Pivot report to the Data Model. There is a checkbox that makes this easy when creating a PivotTable: As so often happens, the analysis grew in scope/importance and I found myself needing to add the data to the data model. While it's not obvious how, there is a way to add an existing Pivot table to the data model. There's a More Tables... link in the PivotTable Fields pane.  Clicking on the  More Tables... results in a dialog confirming that you want to Create a New PivotTable .  Doing so will result in the creation of the new PivotTable in a new sheet. By default the data is added to the data model. You'll likely lose some formatting but for anything other than a trivial PivotTable, this should save effort, as it did for me.
Read more

Getting Started with Mirth (Part 1)

Image
This is the first post in a 2 part series. The second post is here Recently I posted about my positive experience when using Mirth by Webreach as an open source communication layer between one of our in-house applications and a third party and proprietary web service interface. That post received a large amount of attention (relative to my other posts :o) ) so now I will post a quickstart guide to creating a similar setup. In this post I will go over the very basics of using Mirth (please dig in and play around with some more advanced options/configurations), specifically I will demonstrate how to use Mirth to read data from a database, package the data up in a SOAP envelope, send the data to a web service and process the SOAP response. I'll also show you how easy it is to monitor channels once deployed. Once you've installed and opened Mirth for the first time you'll be presented with an empty dashboard - but it wont stay empty for long. This is where you'll s...
Read more

Mirth

Image
Introduction Let's talk about Mirth. At it's simplest, Mirth  link is an Open Source HL7 interface engine. HL7 (Health Level 7) is an NPO involved in the development of healthcare standards and the HL7 v2.x and HL7 v3 standards are commonly used in Medical Information for data interchange - including but not limited to clinical, financial, logistical and administrative messaging. I first ran across Mirth over a year ago on a personal quest to find an alternative to our client's legacy HL7 application. Academically, I wrote a number of lexical analysis tools using lexx, yacc, bison and JavaCC and knew the challenges of writing and maintaining complex parsers. I was simply looking for something that could parse HL7 for us, and perhaps log messages and provide a little more transparency than our application currently allowed.  A year later and our legacy application is still going strong (read: my proposal was declined), but Mirth is being used in production, far away from th...
Read more