Discussion Locked

VB exporting of function names to DLL

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
How do I explicitly export function names to A DLL created by VB so that other programs (in other languages) can call upon a function in the *.DLL ?

4 replies

by easantos

I can create ActiveX DLL's with no problem. The problem is that I cannot access functions in the DLL created by the latest version of Visual Basic. According to the documentation of the Synergy (Dibol) language I am using, I can call functions inexternal DLL's as long as the function names are explicitly exported. I can't seem to find the procedure to do this in the help instructions. Page numbers in the manuals would be helpful. Any web links would be appreciated.

by peter ritchie

VB doesn't "export" function that can be accessed via normal DLL exported functions (e.g. via LoadLibrary() and GetProcAddress()).

VB will allow you, as you've noted, lets you creat standard "ActiveX" dlls that can "export" functionality; but, that's all done through COM.

Unless DIBOL supports COM in the Synergy implementation you'll have to write your dlls in something that can export functions (like C++).

by easantos

This forced me to look elsewhere and find Visual DLL - a product that takes VB DLL and provides function exporting.

This discussion is closed to new replies.