How would I export functions defined in a C# class library, while enabling them to be imported to and called from an unmanaged C++ application/DLL ?
+8
A:
Strictly speaking, you can't just export functions as you would in a classic .dll, as .NET .dll's aren't really .dll's at all. Your only three options are:
- Use managed C++
- Expose your C# classes as COM objects and consume them from your C++ code
- Host the .NET runtime in your C++ project and interact with your C# classes through that.
Adam Robinson
2010-03-11 13:29:28
I see. Many thanks for the quick answer.
shadeMe
2010-03-11 13:42:13
+1
A:
You would not. Not supported. You can pretty much only export COM objects from a C# class librarly.
TomTom
2010-03-11 13:29:28
+1 - COM interop is a fairly standard technique for calling managed code from an unmanaged app.
Tim Robinson
2010-03-11 13:39:39
+1
A:
You could also make a C++ wrapper for your C# library - a simple Managed C++ DLL that would import .NET methods and export them natively. This adds an additional layer, but it might be useful if C# library is a must have.
Another option is to tweak the compiled assembly to export the functions. A C# compiler cannot do this, but it takes a slight change of MSIL code to get the things done. Have a look at this article - there're some links on how the stuff works, and a tool to automate it (though I haven't tried it myself).
VladV
2010-03-11 13:54:23
A C# library isn't a requirement - As a matter of fact, I was considering to use managed C++ instead. I can't use the CLI with my primary application but I can use it to write my library. How would that change the scenario ?
shadeMe
2010-03-11 15:11:50
In this case, you should use Managed C++ - just to avoid unnecessary hacking.
VladV
2010-03-12 09:02:00