Reported by michelpons, 8 years ago.

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.

Reported by jasper, 8 years ago.

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 {

[ComVisible(false)] [Guid("00000109-0000-0000-C000-000000000046")] [InterfaceType(ComInterfaceType.InterfaceIsIUnknown)] public interface IPersistStream : IPersist {

void GetSizeMax(out long pcbSize); int IsDirty(); void Load(IStream pStm); void Save(IStream pStm, bool fClearDirty);

}

}

The propert VTABLE order is {IsDirty,Load,Save,GetSizeMax}. As a result attempting to call Save actually calls GetSizeMax in the above interface.

Reported by michaelhalloran, 7 years ago.

A user was able to install from one directory but not another. The explanation turned out to be that for the directory that failed only the user had rwx permission, but not SYSTEM and the Administrators group. It seems that msiexec needs SYSTEM or admin permission in the source directory to be able to install successfully.