I'm having a little trouble deploying a .NET DLL, and I was wondering
if anyone here could help.

Basically, I've built a DLL to expose some .NET components to COM.
After building the DLL and running "regasm /tlb" and "gacutil", I can
call these components from VB6 on the development machine without any
problem.

The problem arises when I try to deploy this DLL to another machine and
try to call the code from VB6. Once again, I'm using "regasm /tlb" and
"gacutil" to ensure that the DLL is registered with COM. In this case,
Visual Basic "sees" the COM object (i.e., it shows up in the
"References" dialog box under "COM"), but I can't seem to access any of
the NET components. In other words, Intellisense doesn't know about any
of the classes or interfaces declared in the COM object, and trying to
invoke any of these components gives compile-time errors.

What step am I missing/what am I doing wrong?

--Dave