[Mono-list] Porting MS C++ Managed Extensions
Stifu
stifu at free.fr
Wed Sep 30 07:58:49 EDT 2009
Hello,
If you want or need to keep the unmanaged code, you could keep your
unmanaged dll on Windows, and have a "so" counterpart for Linux. That way,
depending on the OS your program runs on, either the dll or so file will be
loaded.
More info: http://www.mono-project.com/Interop_with_Native_Libraries
There is also a project to turn unmanaged invokes into managed invokes, but
I don't think it's mature enough or even usable yet.
More info:
http://squeedlyspooch.com/blog/2009/06/29/minvoke-forcing-portability/
obiwanjacobi wrote:
>
> Hi,
>
> I have this native MS .NET project ( http://vstnet.codeplex.com VST.NET )
> that uses the Microsoft C++ managed extensions to interface between a C++
> plugin interface (VST) and the managed world.
>
> I have received some questions on whether I could make my project
> cross-platform. I think mono wouldn't have any problems with the plain
> .NET code (C#) but its the interop that uses the C++ managed extensions
> that is MS specific.
>
> Is there such a thing as managed extensions on other platforms? Or
> something that would allow me to implement a C++ <-> .NET bridge?
>
> Thanx,
> Marc Jacobi
>
--
View this message in context: http://www.nabble.com/Porting-MS-C%2B%2B-Managed-Extensions-tp25679261p25679603.html
Sent from the Mono - General mailing list archive at Nabble.com.
More information about the Mono-list
mailing list