“The COM library for checking Windows updates does not work according to the C++ MFC source code.”
Environment: Visual Studio 2015, MFC
Is there a way to use RAII techniques in COM?
I am caught between two conceptual models of how to construct objects, and am having trouble working out what standard I want to adopt.
Is there a way to use RAII techniques in COM?
I am caught between two conceptual models of how to construct objects, and am having trouble working out what standard I want to adopt.
Mono: C call into managed with COM Interop
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.
Mono: C call into managed with COM Interop
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.
Mono: C call into managed with COM Interop
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.
Mono: C call into managed with COM Interop
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.
Better to write your .NET library with COM limitations in mind, or separate your .NET library from Interop?
I came across this interesting article: How I Came to Love COM Interoperability on CodeProject, which got me thinking…
Better to write your .NET library with COM limitations in mind, or separate your .NET library from Interop?
I came across this interesting article: How I Came to Love COM Interoperability on CodeProject, which got me thinking…
Better to write your .NET library with COM limitations in mind, or separate your .NET library from Interop?
I came across this interesting article: How I Came to Love COM Interoperability on CodeProject, which got me thinking…