Skip to content

Quick start

Denis Kuzmin [ ] edited this page Dec 28, 2018 · 6 revisions

Configuring the projects

DllExport -action Configure

Since v1.6 provides new manager, you can configure your projects in a few seconds by the following steps below.

[ Quick start (Screencast) 📹 ]

First configuring looks like:

  1. Get latest Manager into solution folder.

  2. Use command -action Configure.

  3. Select some available projects for install operation, then configure this as you need.

  4. (optional) Define storage for your settings to get more automation.

  5. Click [Apply].

Now you're ready to export.

Upgrading DllExport

To update package, all references, and your old manager:

DllExport -action Upgrade {version}

To start export

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

For example:


public static void hello() { }
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


Public Shared Sub hello()
    ' ...
End Sub
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

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


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 PInvoke, you should try to use 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:

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: (wiki: 🗎 Complex types and Strings).


When Conari can help you

... Conari, to me, looks like a dynamic way of doing calling c++ libraries

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.

But yes, the main features is an dynamic way of doing something with any pe-modules (exe, dll) when CLR is host side.

About project types

Our tool still does not provide support of the .net core. Thus, for today, please check that you're trying to use exactly .netfx projects if you have some problems.


  • Our examples are waiting you, here: [ Examples ]
You can’t perform that action at this time.