__declspec( dllexport ) - Calling from vb

[FantastichenEin]

I assumed that using __declspec( dllexport ) meant that I wouldn't have to use a .def file (according to msdn anyway!)

However a dll with __declspec( dllexport ) can still not be called from vb without a .def file.

Any ideas why...


From msdn
----------------------------
These attributes explicitly define the DLL's interface to its client, which can be the executable file or another DLL. Declaring functions as dllexport eliminates the need for a module-definition (.DEF) file, at least with respect to the specification of exported functions
-----------------------------

[Zaei]

__declspec(dllexport) only exports the function. However, it mangles the function name as regular, while VB expects an unmangled function name. You need a def file to accomplish this.

Z.

[CornedBee]

So you can only use those functions with MSVC++-compiled C++.

[Zaei]

Originally posted by CornedBee
So you can only use those functions with MSVC++-compiled C++.

No exactly true... You CAN use GetProcAddress, or use the dll in VB, but instead of using the function name to get the address of the function, you have to use the MANGLED name instead. The def file only stops the mangling.

Z.

[CornedBee]

Have fun using mangled C++ names...

[Zaei]

Originally posted by CornedBee
Have fun using mangled C++ names...

Its not a big deal, you can look at them using the Dependency Walker

Z.

[CornedBee]

Yippeh.

[FantastichenEin]

Thanks for the clarification.