Compiler SDK vs Coder for saving state in c#

I want to export Matlab classes (properties and methods) to use them in C# .NET Framework. I need to save the state of the properties/variables in C#. I am considering this three options and I've found some pros and cons. What would be the best option?

Matlab Compiler SDK

• It generates the DLL assemblies that can be used in C#. For this, I'll need to create the function wrappers (similar to this ) in Matlab, is that correct?
• I want to save the state of the properties stored in the matlab classes (I have machine learning functions that have a learn method and apply method), should I create a matlab wrapper (similar to this again) or it would be better to export only the methods of the matlab class and create the wrapper in C#? The C# wrapper can be a class that has the properties and calls the Matlab methods using the DLLs.

Matlab Code Generator

• It generates C/C++ code. I think once I have them in C/C++ I'll have to create the DLL to use it in my .NET application, is that correct?Is it possible to generate C/C++ code that works on both windows 32b and 64b?
• I'll need to change all my cellarrays to structs since cellarrays are not supported in Matlab Code Generator.

Writting in C# from scratch

• This is probably the best solution in terms of optimized code and testing but It will take me some time to code and debug all my matlab classes. However I am willing to do it if this save me time in the future.

Based on that, what would be the best approach? What are your suggestions?