I met your problem before, it is because c# doesn't recognise the name
of your exported function, go to dos and type:
dumpbin /exports yourdll.dll
you should see the name of your exported function. What happens is
visual c++ "decorated" the name of your fonction for example if your
function name is GetWindowTitle VC++ will export under the mangled name
: ?GetWindowTitle@@blahblah so C# is clueless...
msdn says :
The Microsoft C++ compilers encode the names of symbols in C++ programs
to include type information in the name. This is called "name
decoration", or "name mangling". The purpose of this is to ensure
type-safe linking. The C++ language allows function overloading where
functions with the same name are only distinguished from one another by
the data types of the arguments to the functions. Name decoration
enables the linker to distinguish between different versions of
overloaded functions because the names of the functions are encoded or
decorated differently.
ONE POSSIBLE SOLUTION:
All you have to do is to create and add a file : yourdll.def
you type in it :
; Yourdll.def - defines the exports for yourdll.dll
LIBRARY yourdll
DESCRIPTION 'A C++ dll that can be called from c#'
EXPORTS
YourFunction
Your recompile your dll project to create the updated dll
try again
dumpbin /exports yourdll.dll
You will see your function with the proper name ;)
What you did with the .def file is : you told C# that the name
associated with
[DllImport("C:\\Work\\QuickTimeStreamer\\QuickTimeW rapper\\Debug\\QuickT
imeWrapper.dll")]
private static extern int fnQuickTimeWrapper(); is YourFunction and not
the VC++ decorated name :)
Hope I could help you :) I am sure you will make it!
IRNBRU
*** Sent via Developersdex
http://www.developersdex.com ***