Custom Query (35 matches)
Results (16 - 18 of 35)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#20 | wontfix | Marshal.ReleaseComObject | michelpons | jasper |
Description |
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. |
|||
#19 | fixed | Wrong VTABLE IPersistStream | jasper | |
Description |
Decompiling the interface, I see #region Assembly CAPE-OPENv1-1-0.dll, v1.1.0.0 C:\Program Files (x86)\Common Files\CAPE-OPEN\Reference Assemblies\CAPE-OPENv1-1-0.dll #endregion using System; using System.Runtime.InteropServices; using System.Runtime.InteropServices.ComTypes; namespace CAPEOPEN {
} The propert VTABLE order is {IsDirty,Load,Save,GetSizeMax}. As a result attempting to call Save actually calls GetSizeMax in the above interface. |
|||
#18 | fixed | Silent installation | michelpons | michelpons |
Description |
Is it possible to use the CAPE-OPEN TLBs/PIAs MSIs in a silent installation? If yes, it should be documented. The merge modules may authorize a silent installation but can't be used with installation technology not relying on Windows Installer. Basically it is questionable to bother end-users installing this or that process simulation software with understanding what takes place regarding the CAPE-OPEN TLBs and PIAs, including the acceptation of a specific license model. |