Quick start

Configuring the projects

Starting with v1.6 you can configure your projects in a few seconds by the following steps below through new manager.

Detailed first configuring looks like:

1. Get this (~19 Kbytes) into solution folder. Then, just [Click it] (or command this)
2. Select preferred projects to install and configure as you need.
3. (optional) Define storage for your settings to get more automation.
4. Click [Apply].

Now you're ready to export.

Still not sure? See Various cases in a few steps (Screencast) 📹

To Upgrade Version, use this command. Or starting with 1.7-RC you can also use GUI updater. [?]

To start export

• 🗎 Basic examples for C++ and C#.

To create first exported function, just define DllExport attribute for your favorite static methods.

For example:

C#

[DllExport]
public static void hello() { }

[DllExport]
public static int hello(IntPtr ptr)
{
    return 0;
}

You can also define specific calling convention and custom name:

[DllExport("Init", CallingConvention.Cdecl)]
// __cdecl is the default calling convention for our library as and for C and C++ programs
[DllExport(CallingConvention.StdCall)]
[DllExport("MyFunc")]

VB.NET

<DllExport>
Public Shared Sub hello()
    ' ...
End Sub

<DllExport>
Public Shared Function hello(ByVal ptr As IntPtr) As Integer
    Return 0
End Function

You can also define specific calling convention and custom name:

<DllExport("Init", CallingConvention.Cdecl)>
' __cdecl is the default calling convention for our library as and for C and C++ programs
<DllExport(CallingConvention.StdCall)>
<DllExport("MyFunc")>

See also complete examples, like 🗎 Basic communication with managed .NET libraries from unmanaged native C++

Namespaces

You can configure our tool for any related namespaces in your projects for some additional purpose or just for your convenience in your work.

It's safe because the final modified .net module (.dll or .exe) will not contain any links with our libraries.

The most standardized namespace is System.Runtime.InteropServices. However, we recommend to isolate this within the individual project for future incompatible modification from Microsoft.

About data types

Since this operates under P/Invoke, you need only primitive/scalar types. It will be used anyway through internal marshaling, however, non-scalar types can require additional handling like for managed strings.

About default marshaling behavior you can read here:

• https://docs.microsoft.com/en-us/dotnet/framework/interop/default-marshaling-behavior

So you can try to use MarshalAsAttribute, e.g.: [MarshalAs(UnmanagedType.... Or try to use only scalar types in arguments/return value for your happy using. It's more powerful way to control anything. And it's enough for work with any types, like:

• Pointer to allocated data for any complex types if you need. ~ IntPtr instead of String.

Here, you can also find how to use any structures and strings: https://www.youtube.com/watch?v=QXMj9-8XJnY (wiki: 🗎 Complex types and Strings).

Related:

• Examples Part-1
• Examples Part-2
• Conari

.NET Core based projects

Our .NET DllExport is ready for .NET Core projects starting with v1.7 release

• https://twitter.com/GitHub3F/status/1223291920040058886

When Conari can help you

It was developed for work with any data from unmanaged memory (including native or binary data from the heap) so it can help together with DllExport i.e. even if you have unmanaged host side that will communicate with CLR. You can even access to complex types like structures without their declaration at all.

It also contains different wrappers for types like unmanaged structures, unmanaged strings, and so on. See related screencasts.

This is an dynamic way of doing something with any pe-modules (exe, dll) when CLR is host side.

• https://github.com/3F/Conari

Examples

• Our examples are waiting you, here: [ Examples ]