djinni

djinni copied to clipboard

C# support would allow for easy Windows Phone integration.

http://msdn.microsoft.com/en-us/library/ms235281.aspx shows how to wrap a C++ interface with C++/CLI to allow for use from any .NET language. Does not require generating C#.

I believe it's better to use pInvoke here. Thus your C++ code will be trully native.

Based on the comments, it seems that this issue is not viewed as a necessary change. While calling into native libraries may be trivial, going the other way still requires quite a bit of managed C++ glue code that could be generated. It would be really nice to have support for .NET. While Windows Phone may not represent a large marketshare, support for Windows desktops and tablets is definitely valuable.

+1 for @HoppedUpDev

+1 for @HoppedUpDev

+1 for @HoppedUpDev

GitHub now has reaction, I invite you to use it instead of +1

is there anyone working on this already ?

I doubt it. Windows Phone doesn't seem to be a platform which is worth time investment. Or maybe I missed some other opportunities?

Maybe it would be better to use SWIG here instead of djinni since the former is able to generate C# glue code. If you are using djinni already, you may combine both SWIG and djinni so that djinni generates C++ interfaces that may be parsed by SWIG and generate a glue code. And everything is managed by djinni's IDL.