Interface registrations remain

[jasper]

As a result of the initial 64-bit CAPE-OPEN type libraries being released having component IDs that are equal to the 32-bit type libraries, a side effect of having both installed and removing one after the other in separate installs confuses the microsoft installer tool into thinking that the component has already been uninstalled.

In this scenario interface registrations may remain for the last bitness removed, even if the corresponding files have been removed.

[jasper]

This cannot be addressed for type libraries CAPE-OPEN-1.0.0 and CAPE-OPEN-1.1.0, as the component IDs as they are have already been released and cannot be changed.

The problem is corrected for CAPE-OPEN-1.1-ext and will not be there for any future type library.

[jasper]

The collision of component IDs when including both the 32-bit merge module and 64-bit merge module in the same installer, in addition may cause installer compiler warnings, depending on the installer compiler used.

[jasper]

The problem will disappear upon retiring CAPE-OPEN 1.0 and 1.1.