title: Want to use COM dll file on deployed machines without registering dll files
body: <p>I will make this very simple, as it can get quite confusing very quickly. I have a COM dll (made in VB6) that I would like to be able to use through my C# application. Below are the steps I have taken, and the results.</p>
  
  <ol>
  <li>Created COM dll through Visual Basic 6</li>
  <li>Added COM dll to .Net application.</li>
  <li>Retrieve the "interop.dllName.dll" file generated by .Net in x86/Debug</li>
  <li>Added the <strong><em>interop</em></strong> file as a referenced assembly to my CodeDom generated exe file.</li>
  <li>The CodeDom generated .exe file worked beautifully on my machine when the .exe file was in the same directory as the interop.dllname.dll file</li>
  <li>The CodeDom generated .exe file did <strong><em>not</em></strong> work at all on the deployed machine even though the interop.dllname.dll file existed in the same directory as the .exe file.</li>
  </ol>
  
  <p><strong>Please note:</strong></p>
  
  <ul>
  <li><p>The original COM .dll is not registered on the deployed machine because the deployed machine does not recognize the COM .dll as a valid dll file.</p></li>
  <li><p>The COM .dll was made in a x86 environment, while the deployed machine is running in a x64 environment (does this make any difference)?</p></li>
  </ul>
  
  <p><strong>What my goal is:</strong>
  I would like to be able to have the CodeDom generated .exe file run without the dependency on the interop.dllname.dll file. Is there any way to store these dll files in memory? Also, I do not want my user to have to register the dll files before they can use the CodeDom generated .exe file. Is there any way of going about doing this?</p>
  
  <p>I appreciate any help on the matter. </p>
  
  <p>Thank you for your time,</p>
  
  <p>Evan</p>