title: Issue when registering 32bit COM from outside the system(SysWOW64) directory
body: <p>I'm having an issue in accomplishing the registered state of a 32bit component or library (say <code>OCX</code> or <code>dll</code>), for the purpose of compiling the project directly dependent upon it.</p>
  <p>Standard procedure for achieving it is via regsvr32.exe within SysWOW64 folder pointing to the parameter of component/library destination, e.g. <code>C:\Windows\SysWOW64\regsvr32.exe someComponent.ocx</code> .</p>
  <p>However, after messing with the registry and reinstalling the component the only way I got it working
  was by copying that <code>.ocx</code> and its dependency files into <code>SysWOW64</code>.</p>
  <p>Only then, after using regsvr32(all within the same SysWOW64 folder) Visual Studio compiler managed successfully compiling it, sort of like it was blind to the fact that I've already done that - proven
  in turn by the fact of the presence of the key within the Windows registry.</p>
  <p>Has anyone experienced something like this and why would it register only via &quot;direct&quot; presence of the component within the SysWOW64 system folder as opposed to the &quot;distant&quot; in some other, non-system folder??</p>
  <p>Thanks</p>