How do you call unmanaged code in C#?
💡 Concept: Calling Unmanaged Code from C#
Sometimes, C# alone isn’t enough. Maybe you need to use a Windows API that .NET doesn’t expose, or you want to reuse a fast old C++ library. That’s where unmanaged code comes in — code that runs outside the .NET runtime. In C#, we connect to it using something called P/Invoke.
📘 Quick Intro
P/Invoke (Platform Invocation Services) is like a bridge 🚧 between the .NET world and native libraries. It lets your C# methods call functions inside unmanaged DLLs without rewriting them in C#. You just declare the function signature in C#, and .NET takes care of talking to the native side.
🧠 Analogy
Imagine you’re making an international phone call 🌍📞. - You (C# code) speak one language. - The person abroad (unmanaged code) speaks another. - The gateway operator (P/Invoke) translates everything in real time. If the translation is accurate (correct function signature + data types), the call is smooth. If not, you’ll get gibberish… or the call will drop. That’s exactly how P/Invoke works — a translator between two different worlds.
🔧 Technical Breakdown
- 📥 DllImport: Use the
[DllImport]attribute to point to the DLL and define the function you want to call. - 🛠️ Marshaling: .NET converts your C# types (like
string,int) into native equivalents that C/C++ expects. - 💻 Interop: Works with native C, C++, and Win32 APIs (like
user32.dllorkernel32.dll). - ⚠️ Gotchas: Memory leaks and crashes can happen if you mis-declare the function or forget to free unmanaged resources.
-
📌 Example: Calling the classic Windows
MessageBoxfunction:[DllImport("user32.dll", CharSet=CharSet.Auto)] public static extern int MessageBox(IntPtr hWnd, string text, string caption, int type); // Usage MessageBox(IntPtr.Zero, "Hello from unmanaged world!", "Interop Demo", 0);
🎯 Real-World Use Cases
- ✅ Reusing old but battle-tested C/C++ libraries in modern .NET apps.
- ✅ Calling OS-level APIs (like Windows system dialogs, file operations, etc.).
- ✅ Speeding up performance-critical operations by offloading to native code.
- ✅ Talking to external hardware or drivers that only provide C APIs.
💻 Code Example
using System.Runtime.InteropServices;
class Program {
[DllImport(""user32.dll"", CharSet = CharSet.Unicode)]
public static extern int MessageBox(IntPtr hWnd, string text, string caption, int options);
static void Main() {
MessageBox(IntPtr.Zero, ""Hello from unmanaged code!"", ""P/Invoke Example"", 0);
}
}
❓ Interview Q&A
Q1: What is unmanaged code?
A: Code not managed by the CLR.
Q2: What is P/Invoke?
A: Platform Invocation to call unmanaged DLL functions.
Q3: How do you specify the DLL?
A: Using DllImport attribute.
Q4: What are marshaling concerns?
A: Converting data between managed and unmanaged memory.
Q5: Can you call C++ code?
A: Yes, if exposed via C-style DLL exports.
Q6: Is memory management automatic?
A: No, must be handled carefully.
Q7: Can P/Invoke cause crashes?
A: Yes, if used incorrectly.
Q8: Is P/Invoke supported on all .NET platforms?
A: Mostly, but some restrictions exist.
Q9: Alternatives to P/Invoke?
A: COM Interop, C++/CLI.
Q10: Why call unmanaged code?
A: For legacy or performance reasons.
📝 MCQs
Q1. What is unmanaged code?
- Code outside CLR management
- Managed code
- C# code
- Java code
Q2. What is P/Invoke?
- Calling managed code
- Calling unmanaged DLLs
- Debugging
- Profiling
Q3. How to specify DLL?
- DllImport attribute
- Marshal class
- Namespace
- Assembly info
Q4. What is marshaling?
- Memory allocation
- Data conversion
- Thread management
- Garbage collection
Q5. Can P/Invoke call C++?
- No
- Yes
- Sometimes
- Rarely
Q6. Is memory management automatic?
- Yes
- No
- Sometimes
- Rarely
Q7. Can P/Invoke cause crashes?
- No
- Yes
- Maybe
- Never
Q8. Is P/Invoke on all .NET platforms?
- No
- Mostly
- Yes
- Sometimes
Q9. Alternatives to P/Invoke?
- COM Interop
- Reflection
- Serialization
- Attributes
Q10. Why call unmanaged code?
- For fun
- Legacy or performance
- Testing
- Debugging
💡 Bonus Insight
Calling unmanaged code bridges legacy native libraries with modern .NET applications, enabling powerful integrations.
📄 PDF Download
Need a handy summary for your notes? Download this topic as a PDF!