Assuming your native code is enum shape_type_e { stUNHANDLED = 0, //!< Unhandled shape data. stPOINT = 1 //!< Point data. … }; and your managed code is public enum class ShapeType { Unhandled = 0, Point = 1, … }; You can cast from the native to the managed using shape_type_e nativeST = stPOINT; … Read more
In C++/CLI, use the typeid keyword. e.g. Type ^t = Int32::typeid; In the older “Managed C++ Extensions” syntax, you’d use __typeof(Int32), but that whole version of the language is severely deprecated and you should be using C++/CLI.
It is all the same physical memory. The difference is who is controlling it. The Microsoft definition is that managed memory is cleaned up by a Garbage Collector (GC), i.e. some process that periodically determines what part of the physical memory is in use and what is not. Unmanaged memory is cleaned up by something … Read more
I had a _cdecl c++ dll that I called without any trouble from Visual Studio 2008, and then the identical code in Visual Studio 2010 would not work. I got the same PInvoke … has unbalanced the stack error as well. The solution for me was to specify the calling convention in the DllImport(…) attribute: … Read more
Event Handlers are a very common source of non-obvious memory leaks. If you subscribe to an event on object1 from object2, then do object2.Dispose() and pretend it doesn’t exist (and drop out all references from your code), there is an implicit reference in object1’s event that will prevent object2 from being garbage collected. MyType object2 … Read more
You must always use the Marshal.GetLastWin32Error. The main problem is the garbage collector. If it runs between the call of SetVolumeLabel and the call of GetLastError then you will receive the wrong value, because the GC has surely overwritten the last result. Therefore you always need to specify the SetLastError=true in the DllImport-Attribute: [DllImport(“kernel32.dll”, SetLastError=true)] … Read more
Native code is the code whose memory is not “managed”, as in, memory isn’t freed for you (C++’ delete and C’s free, for instance), no reference counting, no garbage collection. Managed code, you guessed it, is the code whose memory is free and allocated for you, garbage collection and other goodies. Mixed code is when … Read more
Short answer: Managed code is .NET code (VB.NET, C# etc.) that you write and compile to .NET CIL. Unmanaged code is code that is not under .NET that compiles to direct machine code. Long answer: What Is Managed Code? Managed Code is what Visual Basic .NET and C# compilers create. It compiles to Intermediate Language … Read more
You can embed the unmanaged DLL as a resource if you extract it yourself to a temporary directory during initialization, and load it explicitly with LoadLibrary before using P/Invoke. I have used this technique and it works well. You may prefer to just link it to the assembly as a separate file as Michael noted, … Read more
One easy way to call into C++ is to create a wrapper assembly in C++/CLI. In C++/CLI you can call into unmanaged code as if you were writing native code, but you can call into C++/CLI code from C# as if it were written in C#. The language was basically designed with interop into existing … Read more