COMClient easy integration - using generic COMProxy and VAO

Updated with revised VAO source and a revised COMClient sample that properly manages messageloop and the ComConnector ref count. The change in VAO is in VSTAHookup.cs, StopVSTA() method’s last few lines, which causes the connector object to be released immediately: [ mHostItemProvider = null; GC.Collect(); GC.WaitForPendingFinalizers(); ] public void StopVSTA() { // Safely exit debug mode in the VSTA IDE before shutting VSTA down if (mDTE != null) { StopDebugging(); mDTE.Quit(); } try { ExternalDebugging.UnregisterExternalDebugHost(mHostDebugUri); } catch { // Ignore the exception } UnloadAppAddIns(); UnloadMacros(); try { if (mAddInProcess != null) { mAddInProcess.AddInProcessExited -= new EventHandler(AddInProcess_AddInProcessExitedMacro); mAddInProcess.Dispose(); mAddInProcess = null; } } catch { // Ignore the exception } mHostItemProvider = null; GC.Collect(); GC.WaitForPendingFinalizers(); } ============= The other changes – in COMClient.cpp and COMConnector, ConnectorClass.cpp properly manages the messageloop and the Connector ref count for proper shut down. ============= Incidentally, if necessary, your COM application can force the CLR to release all its references to interface ptrs inside RCWs (ie: like VSTA’s reference to CLSID_COMConnector instance) by calling CoEEShutDownCOM() as follows: #include "cor.h" … CoEEShutDownCOM(); This was not necessary in the sample, and usually should not be necessary. Also, your unmanaged application can instruct the CLR to shutdown in an orderly way (includes CLR calling finalization of all unfinalized .NET objects) and exit process by calling CorExitProcess() with passed in error code. This may be needed by pre-VC++7 COM clients to assure that finalization occurs at shutdown as expected: #include "mscoree.h" … CorExitProcess(0); ==========