PInvoke Interop Assistant alternatives and similar packages
Based on the "Interoperability" category.
Alternatively, view PInvoke Interop Assistant alternatives based on common mentions on social networks and blogs.
CefSharp9.7 9.4 L4 PInvoke Interop Assistant VS CefSharp.NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework
pythonnet8.8 4.9 L4 PInvoke Interop Assistant VS pythonnetPython for .NET is a package that gives Python programmers nearly seamless integration with the .NET Common Language Runtime (CLR) and provides a powerful application scripting tool for .NET developers.
CppSharp8.3 5.2 L2 PInvoke Interop Assistant VS CppSharpTools and libraries to glue C/C++ APIs to high-level languages
pinvokeA library containing all P/Invoke code so you don't have to import it every time. Maintained and updated to support the latest Windows OS.
Sharpen5.3 0.1 L3 PInvoke Interop Assistant VS SharpenSharpen is an Eclipse plugin created by db4o that allows you to convert your Java project into c#
CXXI4.1 0.1 L1 PInvoke Interop Assistant VS CXXIC++ interop framework
PyroliteJava and .NET client interface for Pyro5 protocol
LegacyWrapperLegacyWrapper uses a x86 wrapper to call legacy dlls from a 64 bit process (or vice versa).
Access the most powerful time series database as a service
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of PInvoke Interop Assistant or a related project?
PInvoke Interop Assistant
In marshalling there are many attributes and rules for dealing with types. Understanding all of these can be a bit daunting. To improve the development experience, the P/Invoke Interop Assistant was created. It is a tool that conveniently converts C/C++ to managed P/Invoke signatures or verse visa. It even comes with a database of Win32 functions, data types, and constants, so the common task of adding a Win32 P/Invoke to your C# source file is made very easy.
This project is a modernization of the PInvoke Interop Assistant Toolkit which I started almost a decade ago. The intent is to modernize and refactor the code such that it can be consumed as a library and potentially distributed via new channels. For example distribute as a modern VSIX or MSBuild plugin.
This is a hobby project and could definitely use a bit of community participation. Issues will outline the plan for the code going forward.