Need Help: AI 10.5.2 is eating my registry keys - Page 2 - Advanced Installer Community
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Need Help: AI 10.5.2 is eating my registry keys

Hello Roland,
I have send an email with a link to you, containing our setup project and some sample files for registering.
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).
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.
We will analyze this scenario and try to add an improvement in a future version of Advanced Installer. Thank you for your suggestion.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
R.Mueller
Posts: 202
Joined: Thu Aug 02, 2012 3:31 pm

Re: Need Help: AI 10.5.2 is eating my registry keys

Hi Daniel,

Unfortunately this is not exactly the answer I expected. From my point of view, it must be quite common to use the same com libraries for either 32-bit or 64-bit code (with the same registration details), because this needs no special code changes to do so.

In terms of registration with AI, it would be quite easy to handle, when the most keys are reflected to either the 64-bit part and to the 32-Bit part (CLSID and so on), only the registry keys to the physical file location needs to be different.

You have done such great improvements with the registry view inside of the components in organization view. I am pretty sure, you will find a suitable solution in the near future, to make mixed projects more useful.

Hoping the best,

Roland
R.Mueller
Posts: 202
Joined: Thu Aug 02, 2012 3:31 pm

Re: Need Help: AI 10.5.2 is eating my registry keys

Hi Daniel,

what is a workaround to register the same keys for different files in x64 and x86 mode? Currently I am faced with the problem, that the x86 registration is complete. For x64 the CLSID part is also fixed (just solved by a property based key name, as it was possible before). What I am struggling with is the Interface part. The registry view is now hiding this section. Can I also make a fake Interface part (with the help of a property based key name) and copy the expected values?

I tried to move the interface registration into a new component, and marked this component as x64 component. Then the interface is written to HKCR\Interface on both x64 and x86 systems. Unfortunately the wow64 part is missing then on a x64 system (it seems, that the new COM registration is not doing any registry reflection, but it should).

Any help here?

Regards,

Roland
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Need Help: AI 10.5.2 is eating my registry keys

Hello Roland,

You can see my response in the "Handling of COM registration in mixed project types" thread.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”