Marshal.ReleaseComObject

[jasper]

Documentation should mention that for .NET implementations, all external objects must be released using Marshal.ReleaseComObject when they go out of scope. Otherwise .NET will not release the COM objects until GC is invoked, which causes external references to temporary objects to linger, and causes objects to be locked passed Terminate.
It should be mentioned that Marshal.ReleaseComObject will render a COM object inaccessible, so this should not be done on a particular interface to a COM object while other interfaces to the same object must remain valid.
Example: IPersistStreamSave should Marshal.ReleaseComObject the stream pointer within the routine.
Example: objects connected to unit ports should Marshal.ReleaseComObject at Disconnect and Terminate.

[michelpons]

Such an advisory should be part of M&T Integrated Guidelines. Not directly related to the distribution of CAPE-OPEN TLB/PIA by the CAPE-OPEN IDL project.