Wiki Link: [discussion:759]
PowerCommands crashing VS2008 SP1 

Oct 1 2008 at 3:52 AM
Edited Oct 1 2008 at 4:34 AM
I was working on my WPF side project today when I decided to add the WPFToolkit controls to my tool box. At that point visual studio closed without warning. I found an event in the in the application log ".NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A035E00) (80131506)"

Now when I restart VS and try to open an xaml file same thing visual studio closes, same error as above. I googled around and someone suggested uninstalling power commands. I did so and everything is working again. I reinstall and can't design xaml pages.

Here is what is really interesting if I reset the tool box from any tab everything goes back to normal and I can edit xaml files with powercommands installed.

I noticed someone posted a similar isssue when adding toolbox items but for some reason it was considered low priority. I don't know about you but anything that stops this software from working is a really big deal.

I now see that many of the issues in the tracker are related to this toolbox problem.

Oct 16 2008 at 11:55 PM
I'm having a similar crash (same event log error) on VS2008 SP1 while trying to open a web/silverlight project. Just dies while trying to open the solution.

Before this happened, VS2008 got into a state where it was flickering an hourglass on and off, and I finally had to kill the process. After that, it blew up on that solution. Other solutions opened fine. Uninstalling PowerCommands got rid of the problem, but now I don't have PowerCommands.

Oct 22 2008 at 10:28 PM
There is a work around which took some time for me to figure out. However I still seem to be able to corrupt visual studio with the close all files command.

http://social.msdn.microsoft.com/forums/en-US/vssetup/thread/e2434065-9921-4861-b914-9cc9d6c55553

Nick

Oct 30 2008 at 6:07 PM
I have the same problem with it crashing vs.net when viewing some of my .xaml files. It doesn't show an error or anything...vs.net just goes away with no warning. Unfortunately, I can't use this tool until this problem is fixed.

Nov 15 2008 at 6:28 AM
I found an answer that works for me. Please post here if it works for you as well

This is taken from http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/e2434065-9921-4861-b914-9cc9d6c55553/

Thanks to Nick McCready for posting what MS told him to do!

----

Through Microsoft's help they came up with a work around which is a simple modification to the devenv.exe.config file.

This will exist in (64 bit systems) C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE

Or (32 bit systems) C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE

Add this XML token to the dependentAseembly list. They had me add it after the office one, but im not sure if that matters.

<dependentAssembly>
<assemblyIdentity name="office" publicKeyToken="71e9bce111e9429c" culture="neutral"/>
<codeBase version="12.0.0.0" href="PrivateAssemblies\Office12\Office.dll"/>
</dependentAssembly>

<!-NEW STUFF-->
<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>


Now you should be able to run PowerCommands with VS 2008 SP1 and XAML with no crashes. I guess there will be a fix when the next PowerCommands version comes out or on .net 4.0 .

Thanks MSFT!

Dec 3 2008 at 4:30 PM
(On Vista 64) I've found that uninstalling PowerCommands and then reinstalling the latest version (not sure if I had the latest version before) makes the problem go away.

Pete

Feb 27 2009 at 9:21 PM
Edited Feb 27 2009 at 9:25 PM
How do you uninstall Power Commands, I cannot see it in Add Remove Programs ?

Feb 27 2009 at 9:26 PM

mayuresh wrote:
How do you uninstall Power Commands, I cannot see it in Add Remove Programs ?

Thanks I found it

Mar 27 2009 at 2:19 PM
VS 2008 SP1 crashes when I try to Clean or Build an Outlook add-in project. I don't really know waht is the cause, but when I start VS2008 with the /safemode option everything works fine. I think It's due to the PowerCommands tool...
Do you habe any idea !?

Thanks.

Jun 21 2009 at 10:49 AM

<dependentAssembly>
<assemblyIdentity name="office" publicKeyToken="71e9bce111e9429c" culture="neutral"/>
<codeBase version="12.0.0.0" href="PrivateAssemblies\Office12\Office.dll"/>
</dependentAssembly>

<!-NEW STUFF-->
<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>


Now you should be able to run PowerCommands with VS 2008 SP1 and XAML with no crashes. I guess there will be a fix when the next PowerCommands version comes out or on .net 4.0 .

Thanks MSFT!


This helped me on Vista 32 too :) ( I've installed PowerCommands into non-default directory)

Jun 22 2009 at 5:59 PM
Edited Jun 22 2009 at 6:03 PM
I'm receiving the same crash when trying to edit xaml pages. I've tried the config change but that didn't work. Anyone else not had that solve the problem?

EDIT -- Figured it out - should have checked where my PowerCommands were installed to, not "Program Files (x86)" but under "Program Files".

May 5 2010 at 6:42 PM
Neither of suggestions helped with my similar WPF Designer crush. I don't have PowerCommands installed and configuration file contains all mentioned settings.
Here are event messages:

1:
.NET Runtime version 2.0.50727.3603 - Fatal Execution Engine Error (7A2E10D2) (0)

2:
EventType clr20r3, P1 devenv.exe, P2 9.0.30729.1, P3 488f2b50, P4 NIL, P5 NIL, P6 NIL, P7 NIL, P8 NIL, P9 NIL, P10 NIL.

3:
Faulting application devenv.exe, version 9.0.30729.1, stamp 488f2b50, faulting module kernel32.dll, version 5.1.2600.5781, stamp 49c4f482, debug? 0, fault address 0x00012afb.

Any more suggestions ? This is in VS2008.


Updating...
Page view tracker