COM registration of COBIA PMCs: CapeVersion

[jasper]

COM registration of COBIA PMCs takes its information from the registrar. This includes CapeVersion?, which is 1.2 for COBIA PMCs. COM registration should adapt this to 1.1.

[jasper]

-It appears that Aspen HYSYS may be bothered by this in its interop.-

(unconfirmed, probably not)

[jasper]

... the correct version for a thermo providing PMC would be 1.1 - but in principle the unit spec (and others) are still at 1.0. A decision should be taken here.

[jasper]

Replying to jasper:

... the correct version for a thermo providing PMC would be 1.1 - but in principle the unit spec (and others) are still at 1.0. A decision should be taken here.

the decision is compounded by the fact that after 1.0, 1.1, 1.2, CapeVersion? is really going to be replaced by category IDs that indicate the supported CAPE-OPEN versions. Let's discuss.

[michelpons]

My understanding of the discussion held during the M&T SIG meeting on October 18, 2022 is that "when COMBIA is registering a Property Package, a Physical Property Calculator or an Equilibrium Server in the Windows registry, it should store 1.1 as the CapeVersion? and for a Unit Operationn COMBIA should store 1.0 in the Windows registry for the CapeVersion? of that type of PMCs."

[jasper]

... and in addition reporting of COM PMCs to COBIA should adjust CapeVersion? to 1.2

[jasper]

Changing COM registration for COBIA interop, in case capeVersion is 1.2, it is changed to 1.1 for thermo components (identified by catIDs CAPEOPEN::categoryId_PropertyPackageManagerm CAPEOPEN::categoryId_StandAlonePropertyPackage, CAPEOPEN::categoryId_PhysicalPropertyCalculator, CAPEOPEN::categoryId_EquilibriumCalculator) or 1.0. COM components are exposed to COBIA as "1.2" in case capeVersion is "1.0" or "1.1". All example codes and default codes are changed to "1.2"

[jasper]

In [300]:

Fix #131

[jasper]

In [301]:

Fix #131

[jasper]

In [230fa62f3f0f6d562f392d5a70a5b8ac500abe16]:

Fix #131

[jasper]

In [e480e3c0acbfeef3d4f11aa4d15fd9d72d304f22]:

Fix #131

[jasper]

Confirmed that AspenHYSYS is affected by this.