locked
Upgrade a VS2010 Isolated shell to VS2013 shell RRS feed

  • Question

  • I am upgrading a VS2010 Isolated Shell application to VS2013 shell. I am getting following errors in the active logs.

    1.What does the first error mean? how to fix it?

    2. For second error, I saw multiple similar errors associate with different GUID.I searched 4CA58AB2-18FA-4F8D-95D4-32DDF27D184C in registry table, looks like every time when I launch my application, it will overwrite the path of this GUID to pathWhereILaunchApplication\Common7\IDE\PrivateAssemblies*\Microsoft.VisualStudio.TeamFoundation.VersionControlUI.dll, not the Visual Studio installation path, which leads to cannot locate the dll error.

    Can someone help me out of here?

     <entry>
        <record>20</record>
        <time>2014/10/03 18:52:41.650</time>
        <type>Error</type>
        <source>VisualStudio</source>
        <description>Loading UI library</description>
        <guid>{8889E051-B7F9-4781-BB33-2A36A9BDB3A5}</guid>
        <hr>800a006f</hr>
        <errorinfo>Class not registered.
    Looking for object with CLSID: {6C4024E7-5DEC-4EEC-B3F9-55B3F3AD1E9E}.</errorinfo>
      </entry>
      <entry>
        <record>21</record>
        <time>2014/10/03 18:52:42.044</time>
        <type>Error</type>
        <source>VisualStudio</source>
        <description>Loading UI library</description>
        <guid>{4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}</guid>
        <hr>80004005 - E_FAIL</hr>
        <errorinfo>Cannot find the requested resource.</errorinfo>
        <path>D:\branchDir\bin\x86\Debug\ManagementStudio\Common7\IDE\PrivateAssemblies*\Microsoft.VisualStudio.TeamFoundation.VersionControlUI.dll</path>
      </entry>
    Wednesday, October 8, 2014 4:53 PM

Answers

  • Hello,

    I think the two errors are similar, some library path or registry entry may have difference between VS2010 and VS2013 project. You could try to uncommented the related entry in the pkgundef file by the guid in the error message.

    Some related issues that may give you some ideas:

    Migrating VS Shell Isolated 10 to VS Shell 12

    Upgrading VS2010 Isolated Shell Project to use 2012 Isolated Shell


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Marked as answer by Caillen Monday, October 20, 2014 2:02 AM
    Thursday, October 9, 2014 9:39 AM