search

RicoSuter / NuGetReferenceSwitcher

Visual Studio extension to switch between NuGet and project references.
http://nugetreferenceswitcher.org
Microsoft Public License
208 stars 69 forks source link

Package not loading correctly, version 1.5 from extension gallery #11

Closed Cellivar closed 8 years ago

Cellivar commented 8 years ago

image

Shown when clicking the menu option to switch packages. Digging through ActivityLog I found this:

  <entry>
    <record>1147</record>
    <time>2015/11/24 18:56:34.042</time>
    <type>Information</type>
    <source>VisualStudio</source>
    <description>Begin package load [NuGetReferenceSwitcherPackage]</description>
    <guid>{87A7B0E9-E41C-47C8-953C-B81650401EDB}</guid>
  </entry>
  <entry>
    <record>1148</record>
    <time>2015/11/24 18:56:34.081</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>CreateInstance failed for package [NuGetReferenceSwitcherPackage]</description>
    <guid>{87A7B0E9-E41C-47C8-953C-B81650401EDB}</guid>
    <hr>80070002</hr>
    <errorinfo>Could not load file or assembly 'Microsoft.VisualStudio.Shell.12.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.</errorinfo>
  </entry>
  <entry>
    <record>1149</record>
    <time>2015/11/24 18:56:34.081</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>End package load [NuGetReferenceSwitcherPackage]</description>
    <guid>{87A7B0E9-E41C-47C8-953C-B81650401EDB}</guid>
    <hr>80004005 - E_FAIL</hr>
    <errorinfo>Could not load file or assembly 'Microsoft.VisualStudio.Shell.12.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.</errorinfo>
  </entry>

Possibly a bad reference?

Cellivar commented 8 years ago

Coworker is reporting the same thing on his installation.

RicoSuter commented 8 years ago

It works for me, but I also have VS2015 installed... It looks like references a VS2015 DLL... Strange that it worked before, I haven't changed the references...

RicoSuter commented 8 years ago

I've rebuilt the packages with the VS13 and VS15 cmd line tools, try again

Cellivar commented 8 years ago

That did it. I do not have VS2015 on my machine, likely the cause.