Creating and Distributing OCX Interop Assemblies (.NET newbie)

Hello,

I've written several ActiveX controls in VB 6.0, and I would like to make it easier for my customers to use them in VB.NET (or C# etc.). It seems that VS2005 has problems importing some OCXs, so I've taken it upon myself to create what I believe is called a Primary Interop Assembly (correct me if I'm wrong on this...) so they can just add it as any regular .NET assembly rather than dealing with the COM import themselves.

I used AxImp (from 2003) with the source option (to add some attributes, change the namespace, and recompile) and signed with a key created by sn.exe. When I am done, I have three files created by the compiler:

MyControlInterop.dll (the direct result compiling my interop assembly)
MyControl.dll
VBRUN.dll

Plus my original VB6 authored OCX.

I am under the impression that I need to deploy my original OCX, and the MyControlInterop.dll. I think I might also need the generated MyControl.dll, but I'm not sure. What about VBRUN.dll? Do I really need to ship all three + my OCX? :confused:

And if you don't mind an additional question, once I know what files need to be deployed to the developers using my control, how should I go about installing it? Should I be trying to run gacutil from my installer?

Any other advice for a .NET newbie would be greatly appreciated. :o

Thanks,
James