Generate C# P/Invoke signatures for native C/C++ libraries.
npx skills add https://github.com/dotnet/skills --skill dotnet-pinvoke
Please help me install this Agent Skill. Skill: dotnet-pinvoke Source: https://github.com/dotnet/skills/tree/main/plugins/dotnet/skills/dotnet-pinvoke Command: npx skills add https://github.com/dotnet/skills --skill dotnet-pinvoke
This Skill helps developers correctly and safely call native C/C++ libraries from .NET applications, preventing common crashes and data corruption issues.
Use the dotnet-pinvoke skill to generate a C# signature for the native C function int process_records(const Record* records, size_t count, uint32_t* out_processed); given the Record struct definition.
High-intent search queries and answers about installing and using this skill.
Calling a C library from C# requires correctly mapping native function signatures and managing memory lifetime across the managed/native boundary using P/Invoke. This skill generates the exact C# signatures and SafeHandle wrappers needed to prevent interop crashes and data corruption.
Migrating DllImport to LibraryImport for AOT and trimming support involves updating your native interop declarations to use the source-generated LibraryImport attribute. This skill guides the migration process to ensure type marshalling and cross-platform compatibility are preserved.
Marshalling C strings and structs in .NET P/Invoke requires translating native data types into their correct managed equivalents and handling memory allocation properly. This skill provides the correct signature mappings and memory management guidance to ensure safe data transfer.
Your application likely crashes during native code calls due to improper type marshalling, unmanaged memory leaks, or incorrect native handle release. This skill helps debug interop crashes by addressing function signature mapping, memory lifetime management, and SafeHandle usage.
You need SafeHandle when wrapping native libraries to guarantee that native handles are properly released even during asynchronous exceptions. This skill guides SafeHandle usage to ensure robust memory lifetime management across the managed and native boundary.
Yes, you can use P/Invoke for cross-platform native interop in .NET Core by correctly mapping function signatures and ensuring compatible type marshalling. This skill facilitates safe native C/C++ library invocation across different operating systems.
ojrojasGenerate P/Invoke and LibraryImport declarations from C/C++ headers for .NET.
wshaddixConfigure MSBuild for publishing .NET applications with Native AOT compilation.
mo4islonaGuide Rust smart pointer selection for ownership, mutability, and thread safety.
daffy0208Build cross-platform mobile apps with React Native and Expo.
