Examine the exported functions of a 'native' DLL

  • Thread starter Richard A. Lowe
  • Start date
R

Richard A. Lowe

I have a non-COM, non-.NET DLL, apparently written in C++ but for
which there is no source available (so I am told). I have tried the
DumpBin utility and Dependancy Walker to examine the exported
functions so that I can P/Invoke them from C# but I only ever see the
names of the functions, never the full signature. I realize I might
not be able to get the actual as-in-code definition, but there must be
SOME way to infer this, isn't there?

Thanks,
Richard
 
S

Stoitcho Goutsev \(100\) [C# MVP]

Hi Richard,

You can not get function signatures from a native DLL file simple because
they are not there. Native DLLs doesn't have any kind of metadata that's why
you should either know the prototypes or you should have a *.h file.

However, if you have c++ style global function (no c-style) the names are
decorated so if you know the compiler used to build that DLL you may decode
the function prototypes from the function name decoration.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Passing struct of virtual functions 1
exporting my Dotnet DLL as Native DLL? 1
unmanaged code, COM interop vs. exported C functions 3
Can P/Invoke call a native method of a native class? 9
C# DLL with non .NET clients, getting ESP errors 8
Unable to initialize COM in VC Dll when invoked via C# application 7
problem in using exported function in a native DLL 1
Interface to C++ (unmanaged) DLL and std::string or std::wstring 4

Top