Skip to content
Denis Kuzmin [ github.com/3F ] edited this page Aug 10, 2018 · 13 revisions

Start with:

DllExport -action Configure

How to (Screencast)

~ ~ ~ --- ~ ~ ~

Configuring the projects

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

  1. Get DllExport.bat 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 provide exported-functions for unmanaged environments from your managed .NET projects.

To start export

For creating your first function: Just define DllExport attribute for your favorite static methods.

For example:

[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")]

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.

Thus, you need only scalar types in arguments/return value for your happy using. Use pointer to allocated data for any complex types if you need. For example, IntPtr instead of String.

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

Related:

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.

Clone this wiki locally