Hi all,

I recently started dealing with VS .NET, and so far everything is going
good. but a friend of mine approached me with a problem I still can't
find an answer.

He has a VB6 Graph app plotting a chart that uses some DLL files for
"lines". Anytime he needs a new type of "line", he compiled a new DLL,
register it using Regsvr32, and that's all.

He thought of upgrading it to .NET 2003 (or even 2005 if possible). His
idea is that we could try to upgrade one of the DLL he already have and
see the amount of problems it would have.

We did an upgrade of one chosen DLL, resolved all the problems that VS
.NET presented (all of them related to Redim statement or an array size
from 1 to something)

We compiled the DLL, and then we tried to register. Using Regsvr32, it
returns a warning that the DllRegisterServer entry point was not found.
We tried to open the program, and all the DLL created by VB6 are okay,
but the new one are not working.

So we think we may have some problems in the approach. So I would like
to hear some opinions of the following subjects:

- Are we going the right way to upgrade the app? Does a VB6 app works
without problems with a .NET DLL, does the .Net DLL need some changes
to be accepted or the VB6 app would have so much trouble with a .NET
DLL that is better to try to upgrade the app first?

- It seems that regsvr32 is not what we should use to make the .NET DLL
available? If so, any way to make the .NET DLL be registered just like
a VB6 DLL?