I am trying to design a managed library to implement -what appear to be- unmanaged VST3 plugins. The VST3 plugin interface is a C/C++ interface-based API that is compatible with COM (ref-counting, HRESULT etc.) – but is not COM (no reg, CLSID etc). The entry point into the plugin is an exported (on windows) function that retrieves a class factory (much like COM). From there its all COM-compatible interface-based communication.

I am trying to design a managed library to implement -what appear to be- unmanaged VST3 plugins. The VST3 plugin interface is a C/C++ interface-based API that is compatible with COM (ref-counting, HRESULT etc.) – but is not COM (no reg, CLSID etc). The entry point into the plugin is an exported (on windows) function that retrieves a class factory (much like COM). From there its all COM-compatible interface-based communication.

I am trying to design a managed library to implement -what appear to be- unmanaged VST3 plugins. The VST3 plugin interface is a C/C++ interface-based API that is compatible with COM (ref-counting, HRESULT etc.) – but is not COM (no reg, CLSID etc). The entry point into the plugin is an exported (on windows) function that retrieves a class factory (much like COM). From there its all COM-compatible interface-based communication.

I am trying to design a managed library to implement -what appear to be- unmanaged VST3 plugins. The VST3 plugin interface is a C/C++ interface-based API that is compatible with COM (ref-counting, HRESULT etc.) – but is not COM (no reg, CLSID etc). The entry point into the plugin is an exported (on windows) function that retrieves a class factory (much like COM). From there its all COM-compatible interface-based communication.