title: VSIX can't find a static method in another DLL
body: <p><strong>Problem</strong>
   I have a static (extension method) that is referenced in my VSIX project. When I compile the VSIX project, I can see the dll in the bin/debug folder along with the VSIX dll (Same folder).  </p>
  
  <p>In addition, intellisense has no problems with this nor does the compile! When I run the VSIX project in debug mode.  I see this error:</p>
  
  <p><strong>"Method not found: "System.String MethodName(System.String)"</strong>  which is the extension method in another assembly (in the bin/debug folder).</p>
  
  <p>I've read other posts like these:</p>
  
  <p><a href="https://stackoverflow.com/questions/18035790/cant-find-vsix-dlls-with-dllimport">Can&#39;t find VSIX dlls with DllImport</a></p>
  
  <p><a href="https://stackoverflow.com/questions/32811083/include-external-dll-in-visual-studio-extension">Include external .dll in Visual Studio Extension</a></p>
  
  <p>Both solutions don't look right to me, after all, the dll is in the proper folder, it finds its own code, but not the other assembly.... The references and using statements and intellisense work!</p>
  
  <p>This tells me that it's a loader issue, somehow VSIX projects are failing to load other referenced assemblies or maybe it's by design.  </p>
  
  <p>I've tried loading them as Assets but they are not "other" VSIX projects so all of the asset options are out.  </p>
  
  <p><a href="https://i.stack.imgur.com/MZOWl.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/MZOWl.png" alt="enter image description here"></a></p>
  
  <p>Notice however that these asset types are all prefixed with Microsoft.VisualStudio.  I've tried Microsoft.VisualStudio.Assembly and they do not work, in fact it screws up the manifest attempting to do that. </p>
  
  <p>Another oddity, I did include a reference to yet another assembly that comes in as an EXE.  All of those methods work fine.  It's just the dlls that are not getting loaded. For these, I cannot use a USING statement rather, I have to use the fully qualifed NameSpace name to get it to work... But if I try the same trick on the DLLs it doesn't work. </p>
  
  <p>One post suggested adding the assemblies manually to the manifest file... but that post was in 2010.  </p>
  
  <p>This doesn't work either:</p>
  
  <p><em>To include satellite DLLs from referenced assemblies in the VSIX package, add SatelliteDllsProjectOutputGroup to the Output Groups Included in VSIX property.</em></p>
  
  <p>What am I missing?</p>