We have investigated your scenario and, unfortunately, it seems that currently we don't have support to handle (within the same installation project) registration of two COM versions (32-bit and 64-bit one) having common COM registration entries. Currently, this is an Advanced Installer limitation. An improvement will be added in a future version of Advanced Installer, thank you for bringing this to our attention. Until then, as a workaround, you can enable the "Auto register file (DLL,OCX,etc) -> Self register native library" registration option for the 64-bit version of your COM file and the "Auto register file (DLL,OCX,etc) -> Extract registration info from native library" option for the 32-bit version of your COM file, or vice versa. Also, as another option you could create two different installation project (one for 32-bit files and one for 64-bit).I have send an email with a link to you, containing our setup project and some sample files for registering.
We will analyze this scenario and try to add an improvement in a future version of Advanced Installer. Thank you for your suggestion.Furthermore I would like to add, you should consider converting existing registry keys into com view items, otherwise its hard to distinguish between them and where they are belong to and how to fix any registration issues. As stated, the biggest pain is having the same keys in two components with different installation folders and registry locations. There is no easy way to find out, if they are complete or not.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging