Visual Studio Developer Center >
Visual Studio Forums
>
Visual Studio Setup and Installation
>
Xaml Editor, Class Explorer Crashes after Visual Studio 2008 SP1
Xaml Editor, Class Explorer Crashes after Visual Studio 2008 SP1
- 0Please Read the following post. I started this post because my problem is not solved and it seems my problems with VS 2008 SP1 are just getting worse.
Along with opening XAML files now my Class Explorer crashed Visual Studio 2008 SP1 with no warning or exceptions.
Below is where I began.
Xaml Editor Crashes after Visual Studio 2008 SP1
Currently I am reinstalling VS 2008 and then SP1
I am running VS 2008 Developer Edition with Team Exploerer and VS 2008 Power Commands.
Answers
- 10Through 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!
- Marked As Answer byNick McCready Tuesday, August 19, 2008 7:24 PM
- Edited byNick McCready Monday, September 08, 2008 2:13 PMspelling
- 0As it turns out through Microsoft support it is Power Commands 2008 that causes the problem for me. As soon as it was uninstalled the errors when away. They are looking into now and searching for hot fixes or workarounds. So Power Commands 2008 has compatibility problems with VS 2008 SP1 . Hope this helps some one!
- Edited byNick McCready Friday, August 15, 2008 6:47 PMfix spelling
- Marked As Answer byNick McCready Friday, August 15, 2008 6:47 PM
All Replies
- 0
Thank you for taking the tmie to post this. Your solution worked perfectly.
- 0No problem, your welcome! :)
- 0I've been looking for a fix, let alone an acknowledgment of this problem for quite a bit, thank you very much.
- 0Hey just give me a bump with the "Post was helpful" : D
- 0Perfect!! I too had a hard time finding an answer to this.
thanks again. - 0Invaluable assistance this post provided!!
Shawn Cicoria - 0The problem is, Vista won't allow me to save that file. What OS are you running?
- 0To save the file you need to run Notepad elevated (Run as Administrator) then you will be able to save no problem. This is the way it is with any file below C:/ProgramFiles/ or even C:/Windows. This is to protect people from making changes if they dont know what they are doing. It also protects against rogue programs because unless they are elevated they cannot delete everything under the sun. UAC is really a good thing. You can lower the prompting though the Security Policys.
