Need Help: AI 10.5.2 is eating my registry keys - Advanced Installer Community
R.Mueller
Posts: 202
Joined: Thu Aug 02, 2012 3:31 pm

Need Help: AI 10.5.2 is eating my registry keys

Hi,

I tried to add some missing registry keys (for a component, which was not correctly registered). While doing so, I found out, that my registry view is missing the whole HK_CR\Interface part (with a lot of sub keys). First I was shocked and assumed that they got deleted :shock: ... fortunaltely not, but it seems they are not displayed anymore.

I checked my project file (and found the keys). Then I added a new key under HK_CR\Interface and it was shown under the according component. As soon as I restarted Advanced Installer, the key seems to be vanished as well. If I scroll down in the component view, I can still find the missing interface registrations, but a keypress on F8 (Goto Definition) does only show the registry key view, but not the key itself (this seems to be a follow up problem, hence the key is not listed there).

Also the registry table is missing those keys, only the project file still contains the keys.

Is my project file corrupted? Is the result MSI affected or is this just an AI UI problem?

Regards,

Roland
Teodor
Posts: 73
Joined: Thu Jul 25, 2013 9:56 am

Need Help: AI 10.5.2 is eating my registry keys

Hi
R.Mueller wrote:I tried to add some missing registry keys (for a component, which was not correctly registered). While doing so, I found out, that my registry view is missing the whole HK_CR\Interface part (with a lot of sub keys). First I was shocked and assumed that they got deleted :shock: ... fortunaltely not, but it seems they are not displayed anymore.

I checked my project file (and found the keys). Then I added a new key under HK_CR\Interface and it was shown under the according component. As soon as I restarted Advanced Installer, the key seems to be vanished as well.
The HK_CR\Interface registry subkeys can now be more easily managed from the COM page starting with Advanced Installer v10.3.
R.Mueller wrote:If I scroll down in the component view, I can still find the missing interface registrations, but a keypress on F8 (Goto Definition) does only show the registry key view, but not the key itself (this seems to be a follow up problem, hence the key is not listed there).
Indeed, pressing F8 on these registry keys should open the COM page instead of the Registry page. Thanks for pointing out this issue.
R.Mueller wrote:Also the registry table is missing those keys, only the project file still contains the keys.
Looking at and old version of your project I can see the entries. Please check again.
R.Mueller wrote:Is my project file corrupted? Is the result MSI affected or is this just an AI UI problem?
This is not a problem, but only a user interface reorganization to make it more simple and intuitive.

If you have other questions, please let us know.

Best regards
Teodor Micu - 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 Teodor,

ok, I see the point. So, for the moment, I can still add new interfaces via the registry view?

So, an import function is missing, and it is not possible to find out, to which components the interfaces belongs to (but this is important). The Organization View needs also some updates, to show the com interfaces correctly (not with registry icon, with com icon). F8 should also work in both ways.

But thanks for helping so far.

Regards,

Roland
Teodor
Posts: 73
Joined: Thu Jul 25, 2013 9:56 am

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

Hi
R.Mueller wrote:ok, I see the point. So, for the moment, I can still add new interfaces via the registry view?
Yes, you can add new Interfaces in Registry view but next time you open the project these will be displayed in COM view. Why not use a better, more specialized UI from COM view?
R.Mueller wrote:So, an import function is missing, and it is not possible to find out, to which components the interfaces belongs to (but this is important). The Organization View needs also some updates, to show the com interfaces correctly (not with registry icon, with com icon). F8 should also work in both ways.
Indeed, the Interfaces should appear in the Organization view. Thanks for the notice.

Advanced Installer is constantly improved in several areas, but the most important factor is the feedback we receive from you!
Teodor Micu - 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 Teodor,

No question, I appreciate any changes to improve the user interface, especially the Registry View is a pain (see my post here).

With my project, the com view looks currently like this:
COM_View.png
COM_View.png (116.75 KiB) Viewed 15766 times
I just missed my registry keys in the first hand, I am glad to find them somewhere else. After some testing and playing around with this new view, I found it not so helpful yet, but I looking forward for improvements you will do in this area. Furthermore its currently quite impossible to find out, which interface belongs to which component. Also some import functions would be required: like import from registry or import from dll/typelib.

Is it planned, that AI will also integrate the COM classes and Typelib registration into that view?

Regards,

Roland
Teodor
Posts: 73
Joined: Thu Jul 25, 2013 9:56 am

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

Hi
R.Mueller wrote: ... its currently quite impossible to find out, which interface belongs to which component.
As noted in my previous post, we'll add the Go to Resouce (or F8) for Interfaces in a future version of Advanced Installer.
R.Mueller wrote:Also some import functions would be required: like import from registry or import from dll/typelib.
Yes, this is on our development list too. Note that you can already use this function from the Registry view.
R.Mueller wrote:Is it planned, that AI will also integrate the COM classes and Typelib registration into that view?
Advanced Installer already has support for them in COM view.

Best regards
Teodor Micu - 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 Teodor,
Advanced Installer already has support for them in COM view.
Yes, but unlike the interfaces, they are not removed from registry view and do not appear in COM View automatically. Furthermore, as far as I know, that a recommendation from Microsoft exists, to not use the MSI integrated typelib tables for registration of typelibs. Its recommended to use the registry view as I do.

Nevertheless, I just wanted to know if any changes in this area are also planned for the future?

Regards,

Roland
Teodor
Posts: 73
Joined: Thu Jul 25, 2013 9:56 am

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

Hi
R.Mueller wrote:Yes, but unlike the interfaces, they are not removed from registry view and do not appear in COM View automatically.
We've added this issue to our development list.
R.Mueller wrote:Furthermore, as far as I know, that a recommendation from Microsoft exists, to not use the MSI integrated typelib tables for registration of typelibs. Its recommended to use the registry view as I do.

Nevertheless, I just wanted to know if any changes in this area are also planned for the future?
Indeed, we are using typelib from Windows Installer. We already have several improvements on our development list.

Best regards
Teodor Micu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
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,
As noted in my previous post, we'll add the Go to Resouce (or F8) for Interfaces in a future version of Advanced Installer.
This improvement was added in version 10.8 of Advanced Installer released on December 10, 2013.

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,

thats great, I will check this out after AI 10.8 is out.

Regards,

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,

currently I am working with AI 10.9.1 and I am still faced with some problems with the F8 key on some places (it jumps to the registry view without finding the related entry instead going to the com view and highlighting the related entry here).

But the most important problem or question on my side is handling of mixed 32-bit/64-Bit projects. How do I create the right keys in com-view for the right component? Is there any possibility to change the values created in the registry depending on the output type? Usually you have the same registry keys for CLSID and Typelib, but filled with different values (especially the typelib, sometimes also the CLSID, depending on the registered values), after my experience, the Interfaces part is the same on both 32-/64-Bit systems. In the past I often used a special property based CSLID64 Key for creating those entries (this was a recommendation by Bogdan). How do I handle double keys with the new COM view? Are there any improvements planned for the next version, especially for mixed projects?

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,
currently I am working with AI 10.9.1 and I am still faced with some problems with the F8 key on some places (it jumps to the registry view without finding the related entry instead going to the com view and highlighting the related entry here).
Indeed, this may happen after you manually create the related COM entries in "Com" page. This is an Advanced Installer limitation. We will try to add and improvement regarding this in a future version of Advanced Installer, thank you for bringing this to our attention.
But the most important problem or question on my side is handling of mixed 32-bit/64-Bit projects. How do I create the right keys in com-view for the right component? Is there any possibility to change the values created in the registry depending on the output type? Usually you have the same registry keys for CLSID and Typelib, but filled with different values (especially the typelib, sometimes also the CLSID, depending on the registered values), after my experience, the Interfaces part is the same on both 32-/64-Bit systems. In the past I often used a special property based CSLID64 Key for creating those entries (this was a recommendation by Bogdan). How do I handle double keys with the new COM view? Are there any improvements planned for the next version, especially for mixed projects?
In order to achieve this you should add the COM source files (the 32-bit and 64-bit files) in our "Files and Folders" page, enable their "Register .NET assembly for COM interoperability" registration option, and make sure the COM components are added accordingly under 32-bit and 64-bit features. Also, the 64-bit COM component should be marked as "64-bit Component".

Let us know if this helped.

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,

does this means, I can add the same classes, typelibs and interfaces again to the com view, as long as i add them to different components, which are marked x64 or x32?

The pain is here, that you need to import the definitions via the registry import, so its a pain to add a larger number of CLSIDsor Interfaces.

In my case, I have classical c++ dlls with COM. Usually I only add new classes or interfaces manually to the setup. The first run nevertheless, was done with "register for COM", but without synchronization configured. Mostly I have two dlls with the same name and classes inside, but one is for 32-Bit and one build for 64-bit. How would I add them properly with correct registration for each?

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,

In order to have a better view of your COM registration scenario could you send us both versions, 32-bit and 64-bit, of your COM to support at advancedinstaller dot com so we can take a look? If you cannot make a disclosure of their source files we would really appreciate if you could send us two sample COMs (32-bit and 64-bit one) similar with your original COMs. Currently we are performing a major refactoring of our COM registration support and analyzing your COMs scenario could also help us to improve our COM registration functionality.

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,

I have send an email with a link to you, containing our setup project and some sample files for registering.

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.

I am keen for your feedback.

Regards,

Roland

Return to “Common Problems”