Home/ Questions/Q 8770803
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T17:37:52+00:00

I want to implement a Mongoose (http://code.google.com/p/mongoose/) Binding in C#. There are some examples,

  • 0

I want to implement a Mongoose (http://code.google.com/p/mongoose/) Binding in C#. There are some examples, but they don’t work with the current version.

This is my current function call:

[DllImport("_mongoose",CallingConvention=CallingConvention.Cdecl)] private static extern IntPtr mg_start(int zero, Nullable, string options);

The (working) C equivalent would be:

const char *options[] = {
     "document_root", "/var/www",
     "listening_ports", "80,443s",
     NULL
   };
struct mg_context *ctx = mg_start(&my_func, NULL, options);

where mg_start is defined as:

struct mg_context *mg_start(mg_callback_t callback, void *user_data,
                            const char **options);

You can find the whole C example here:
https://svn.apache.org/repos/asf/incubator/celix/trunk/remote_services/remote_service_admin_http/private/include/mongoose.h

How do I transfer the const char *options[] to c#?

Thank you

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team
    DllImport("_mongoose",CallingConvention=CallingConvention.Cdecl)]
private static extern IntPtr mg_start(IntPtr callback, IntPtr userData,
    [In][MarshalAsAttribute(UnmanagedType.LPArray,
                            ArraySubType=UnmanagedType.LPStr)] string[] options);

    Haven’t tried this, but I think this gets you there. You might need to make the ArraySubType be LPWStr if you want unicode in the C call. Making it LPStr gives you ANSI.

    Are you doing the function pointers? That’s where the real challenge is. Not so much from declaring and marshaling but rather from a pointer lifespan issue. If mg_start holds onto the unmanaged version of the delegate, you may find that the thunk gets garbage collected on you, in spite of what the documentation says. We’ve seen this happen so often that we’ve, where possible, rearchitected the underlying glue to not use that style of code.

    Generally speaking, if the API is a chatty API with tons of callbacks, you’re going to be hosed by the callbacks. You’re better off trying to create a C++/CLI library that implements the API in a far less chatty way with clear managed/unmanaged boundaries.

    • 0