const-me/comlightinterop

Cross-platform COM interop library for .NET Core 2.1 or newer

comlightinterop's Issues

'IUnknown': ambiguous symbol

ComLight::IUnknown is conflicting with IUnknown in file ocidl.h

Excerpt of the compiler output. The other lines are almost similar error messages

2>C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um\ocidl.h(463,14): error C2872: 'IUnknown': ambiguous symbol
2>C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um\unknwnbase.h(109,9): message : could be 'IUnknown'
2>C:\Users\Name\source\repos\TempProj\ComLightLib\unknwn.h(26,27): message : or 'ComLight::IUnknown'

a Temporary project (.Net5) was added to github:
raymrdc/TempProj

Can i create COM server from VTABLES (generated by your library)

I was inspired by this article
https://www.codeproject.com/Articles/13601/COM-in-plain-C
They generate Vtables and use them in C. Your library allos generation of VTABLES from managed code..

Does ComLight work for .NET client and 3rd party unmanaged server with COM compatible interfaces?

Hi, you pointed me towards your project in a github discussion about use-cases for cross-platform COM interop.

I am wondering if ComLight will fix the following scenario:
I am building a .NET5 library for working with the VST3 (Steinberg) interface specification. The VST3 C++ plugin interface specification is for working with Audio/MIDI plugins inside a Digital Audio Workstation (DAW) - (usually) a multitrack recording application. The goal of my library is to make it possible to write VST3 plugins (and hosts) in .NET without having to know C++. The VST3 C++ interfaces are all COM compatible (derive from IUnknown, return HResult) and so I am looking for an easy way to do the marshalling.

The question is: will ComLight (.NET client) work if I have no control over the unmanaged COM interfaces?