You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After playing with SharpGen for a bit I got the first code generate (yeah!).
This raised some questions I hope you can answer for me.
Can SharpGen generate C# interfaces?
The generated code I get is mainly focused on wrapping unmanaged object/interface pointers to be called from C#. I also need the other direction where unmanaged code will all into C# interfaces (vtables?) that are to be implemented. Both ways require marshaling?
How to use the generated code output and assembly icall rewriter?
I have not found any docs on this. Currently the generated code ends up buried in the obj folder. How is this intended to be used in a project?
Is it possible to generate code for any SharpGen.Runtime dependencies and not use the runtime assembly?
I would prefer to create a self contained assembly with all my interfaces, structs and interop.
The answers to these questions will help me decide if to use SharpGen or build my own using the new ComWrappers API.
The text was updated successfully, but these errors were encountered:
Noob here, again.
After playing with SharpGen for a bit I got the first code generate (yeah!).
This raised some questions I hope you can answer for me.
The generated code I get is mainly focused on wrapping unmanaged object/interface pointers to be called from C#. I also need the other direction where unmanaged code will all into C# interfaces (vtables?) that are to be implemented. Both ways require marshaling?
icall
rewriter?I have not found any docs on this. Currently the generated code ends up buried in the obj folder. How is this intended to be used in a project?
I would prefer to create a self contained assembly with all my interfaces, structs and interop.
The answers to these questions will help me decide if to use SharpGen or build my own using the new ComWrappers API.
The text was updated successfully, but these errors were encountered: