dllimport

I am writing a DLL for a third party application. The main software engineer mentions that the application uses the __cdecl (/Gd) calling convention. That I need to make sure that I use that. Additionally, the third party has provided to me a C++ DLL skeleton which exports the functions as follows: #ifdef _EXPORTING #define DECLSPEC __declspec(dllexport) #else #define DECLSPEC __declspec(dllimport) #endif #ifdef __cplusplus extern "C" { #endif DECLSPEC int ICD_Create(char* id); .... .... I am kind of confused. Why the functions are being exported using __declspec convention instead of __cdedl?

My application uses one version of library (a.dll), I am using another DLL(b.dll) which in-turn uses older version of the same library (a.dll) that i use. I am building the application by embedding a manifest file. The DLL i use is also using a embedded manifest file. I am having both the versions of the library in my WinSXS folder. My application is not able to load the appropriate versions of DLLs. Will having a separate manifest file (not embedding into DLL) help resolving the problem? What is the work around? Your situation is exactly the situation WinSxS is supposed to solve. It should be

I was re-reading through some .Net documentation today when I noticed that the first portion of the extern keywords documentation claims: The extern modifier is used to declare a method that is implemented externally. A common use of the extern modifier is with the DllImport attribute when you are using Interop services to call into unmanaged code. What caught my attention was that the document states that "a common use" of extern is that it is used with the DllImport attribute. This implies that there are other use-cases where DllImport is not required. I've not had to integrate many external

A .NET application calls C dll. The C code allocates memory for a char array and returns this array as result. The .NET applications gets this result as a string. The C code: extern "C" __declspec(dllexport) char* __cdecl Run() { char* result = (char*)malloc(100 * sizeof(char)); // fill the array with data return result; } The C# code: [DllImport("Unmanaged.dll")] private static extern string Run(); ... string result = Run(); // do something useful with the result and than leave it out of scope Some tests of it show that the garbage collector does not free the memory allocated by the C code.

Given this C API declaration how would it be imported to C#? int _stdcall z4ctyget(CITY_REC *, void *); I've been able to get this far: [DllImport(@"zip4_w32.dll", CallingConvention = CallingConvention.StdCall, EntryPoint = "z4ctygetSTD", ExactSpelling = false)] private extern static int z4ctygetSTD(ref CITY_REC args, void * ptr); Naturally in C# the "void *" doesn't compile. Some Googling indicates that it should be translated as "object." Which seems like it should work. But others indicate that "Void * is called a function pointer in C/C++ terms which in C# terms is a delegate". That doesn

I think I have basically understood how to write c# delegates for callbacks, but this one is confusing me. The c++ definition is as follows: typedef int (__stdcall* Callback)( long lCode, long lParamSize, void* pParam ); and my c# approach would be: unsafe delegate int CallbackDelegate (int lCode, int lParamSize, IntPtr pParam); Although this seems to be incorrect, because I get a PInvokeStackInbalance error, which means my definition of the delegate is wrong. The rest of the parameters of the function are strings or ints, which means they cannot cause the error, and if I just pass a IntPtr

I'm trying to access an unmanaged library and am lucky to have access to a comprehensive guide to the API. Unfortunately, I've no idea what the C# equivalent of C++'s WORD type is. Similarly, I've no idea what DWORD would be. yan You're probably looking for ushort for WORD and uint for DWORD. 来源： https://stackoverflow.com/questions/5490428/whats-the-equivalent-of-word-in-c