Задайте вопросЗадайте вопрос
 

ОтвеченоXaml Editor, Class Explorer Crashes after Visual Studio 2008 SP1

Ответы

  • 19 августа 2008 г. 19:23Nick McCready Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     Отвечено
    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!
    • Помечено в качестве ответаNick McCready 19 августа 2008 г. 19:24
    • ИзмененоNick McCready 8 сентября 2008 г. 14:13spelling
    •  
  • 15 августа 2008 г. 18:47Nick McCready Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     Отвечено
    As 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!


    • ИзмененоNick McCready 15 августа 2008 г. 18:47fix spelling
    • Помечено в качестве ответаNick McCready 15 августа 2008 г. 18:47
    •  

Все ответы