I've been looking into potentially using Noesis for my project where i'm doing a hybrid C++ C# solution and after evaluating both the Managed SDK and the Native SDK neither seem to directly cover my usecase. Where i wanted to implement many platform implementation details directly in C++ but leave ui details such as the code behind to be implemented within a C# scripting runtime.

I see that the C# API layer basically is just a SWIG wrapper around the C++ api and i was wondering if there is an option to have the SWIG api layer distributed either as a separate shared library, or a combined library with both the C++ exports and the SWIG exports.

Best Regards,
Matthew

Thanks for getting back to me, yes we are a very small indie company just getting started on our journey :)

I'd assume there is no other options for the moment then, I've been spending a bit of time with various tools trying to generate bindings to the Native C++ library myself with little luck and the scope is too large to just do it manually.

If you can consider exposing the C++ API from within the managed libraries that would be ideal for us as the size isn't a huge concern for us, but i understand if you guys don't want to.