title: .NET interop COM DLL behaves differently in VB6 debugger
body: <p>I have a .NET v2.0 Dll that exposes a few classes to COM. The assembly is called BLogic.DLL</p>
  
  <p>I'm calling these classes from a legacy visual basic 6.0 application. I can generate and EXE file and if I have Blogic.dll in the same folder as the EXE, the program runs without a hitch.</p>
  
  <p>However If I try and launch the same program within the VB6 debugger I get a:</p>
  
  <pre><code>   Automation Error    
     The system cannot find the file specified
  </code></pre>
  
  <p>I assume when I'm running in the debugger, the PLogic.dll file can't be found. I tried putting it in the System32 folder, and the same folder as the VB6.EXE file, but I still get the same error.</p>
  
  <p>Other facts that may help:</p>
  
  <p>PLogic.dll is NOT a strongly-named assembly. It depends on a 3rd party reference that isn't strongly signed so VS doesn't let me strongly sign it. However the 3rd party functionality isn't being called by the VB6 code, and it is not ComVisible.</p>