dotnet-pinvoke

To call native C/C++ libraries from .NET using P/Invoke, you define external methods with correct function signatures and marshal data types across the managed/native boundary. This Skill automates generating accurate P/Invoke declarations from C/C++ headers.

Handling string marshalling and memory ownership in .NET interop requires explicit encoding specifications and safe memory allocation tracking. This Skill provides guidance on proper string handling and memory management to prevent leaks at the native boundary.

Mapping native types to .NET types for native interop involves translating C/C++ primitives and structures to their managed equivalents. This Skill ensures type mapping precision to maintain data integrity when integrating native libraries.

Yes, this P/Invoke guidance applies to both .NET Framework and .NET Core/5+ applications requiring native library integration. It supports writing both traditional P/Invoke and modern LibraryImport declarations.

Crashes or memory leaks at the managed/native boundary typically occur due to incorrect P/Invoke signatures, improper string marshalling, or mishandled memory ownership. This Skill helps debug these issues by ensuring accurate type mapping and safe error handling.

Using LibraryImport for native library integration involves creating source-generated declarations for calling unmanaged code. This Skill guides you in writing new LibraryImport declarations from C/C++ headers to efficiently interoperate with native libraries.