Examine the exported functions of a 'native' DLL

[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

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

--
B\rgds
100

"Richard A. Lowe" <ch*****@yahoo.com> wrote in message
news:2a**************************@posting.google.c om...

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