🚀 go-pugleaf

"mauro" <m.russo@uniplan.it> wrote in message
news:473ed1eb$1@newsgroups.borland.com...

> When I generated the project I chose only the options "C++" and
> multi-thread.

In other words, you use the "File > New > DLL Wizard" option?  If so, then
you do ot need to worry about DllRegisterServer() at all.

> Really, I am very interested to learn how to export classes from a DLL.

You can't.  Even if you could, you wouldn't be able to import them into
non-Borland compilers.

> In fact, my DLL has a class to export, but I did not know
> how to do it

Don't even try to go that route to begin with.

> I exported functions to manage the class.

That is what you have to do.

> Then, when we used in Borland Delphi, we used a Delphi class
> which uses the exported function, in order to have in Delphi a
> class exactly as that in the DLL.

For Delphi and C++Builder, it would be better to make a Package instead of a
DLL.  Then you can use the original class directly.  In order to support
non-Borland compilers, you will have to continue with the function approach.

> My friend, working on VS, is used to register every DLL.

Again, that only applies to DLLs that host COM objects specifically.  It
does not apply to all DLLs in general.  Certainly not the kind of DLL you
have made.

> He thinks that he needs to register the DLL in order to use it.

He's mistaken.

> I believe the point is that he is using C# and so I could not
> tell him how to translate in C# the way I use in C++ to use
> the DLL

.NET languages, such as C#, need to use PInvoke to access unmanaged DLLs.
C++Builder does not produce native .NET assemblies.  You need Delphi.NET for
that.


Gambit