Visual Basic dll

[loadman]

Hi,

Is there any way of producing a dll in VB6 and/or VB.net to be called like a C++ or Delphi one would.

From my 'googling' VB6 is not and option but you can call vb.net dll's but you have to call them a different way.

What I want to do is make another MaLa plug-in template in VB without Swindus having to change any code. There is allready a C++ and Delphi example in the SDK .

EG:
C++:
extern "C" DLL void MaLaGameStart()

Delphi:
procedure MaLaGameStart(); cdecl;

Does anyone know of a way to produce VB Dll's that you can export functions/procedures this way?

Thanks 

[Howard_Casto]

The short answer is no.  Vb6 dlls aren't "real" dlls so they require different interface methods.  I'm not as familair with .net, but judging by what you said, I'll bet they inherited this trait. 

[loadman]

The short answer is no.  Vb6 dlls aren't "real" dlls so they require different interface methods.  I'm not as familiar with .net, but judging by what you said, I'll bet they inherited this trait. 

Thanks Howard. 

 I've seen some work arounds but they are not straight forward.    Not worth it for this task anyway. 

Maybe I could make a Plug-in that reads VB Plug-ins.....  Maybe I'm being silly now   

[arzoo]

The short answer is no.  Vb6 dlls aren't "real" dlls so they require different interface methods.  I'm not as familair with .net, but judging by what you said, I'll bet they inherited this trait. 

VB6 and .net are very different. That being said, a DLL created with VB.net still can't export functions like with C++ or Delphi. A DLL created in VB.net is an assembly which can only be used by other .net assemblies. It's my understanding the only way a DLL created with VB.net can be used by other languages is to expose it's interface via COM.

Hi all
       I am a new member to this group. can I know if VB6.0 dll are not real them why r we using these.
Thnx.
Love Songs   

Gospel Music   

VB is not widely used for MAME development. I believe Loadman posted this thread more for "academic" reasons.

[Howard_Casto]

It's not widely used fo rmame development, but it IS widely used for fe development.  I don't have any clue how mame comes into the equation here.

[arzoo]

It's not widely used fo rmame development, but it IS widely used for fe development.  I don't have any clue how mame comes into the equation here.

Howard,
By "mame development" I was referring to all things mame (not specifically the emulator code) - sorry for the confusion. I wasn't under the impression that VB was popular for fe stuff, but you've been doing this for way longer than I have, so I defer to your assessment. 

[Havok]

Don't mind Howard, he's just grumpy because he's lonely and not married...

 

[loadman]

Don't mind Howard, he's just grumpy because he's lonely and not married...

 

He is married to the Hobby of developing and assisting us Retro Gaming folk.   

I have appreciated his help so I let the occasional grumpy stuff slide 

But back to VB...  Yeah my reasearch confirms waht you all tell me. 
It is confuslling as they are both called Dll's
Mayben there should be a name like:
Com Dll''s for and Win32 Dll's