🚀 go-pugleaf

>> 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.

Yes.

>> 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.

We did that, with the class written in Delphi. Really we also wrote a 
discendent class in Delphi
to manage something automatically and we transformed this second class in a 
Package.
Moreover we used that Pascal code compiled in C++ Builder, to obtain an 
equivalent
package.

> .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.

Thank you for the information.
I believe we shall translate the Delphi code in C#.

A last question.
If we use DELPHI .net, we will be able to export classes (in any way, COM 
object, package or everything else)?

Thank you.