Default programs

[ChristianLA]

Hi:

We are implementing the Default Programs using ADV INST 10.3 to set the file association to our apps, these apps have its own installer but they use the same file extensions, from here I have a couple of questions:

- After the installation when you click the associated file or change the default program the Windows Installer windows launches itself to execute some (related) task, I have tried other apps (external apps) and they don't show the windows installer they just change the default, is there a way to avoid this?

-If we have two apps in the installation that use the same extension and need to be in the Default Programs list so the user can choose which of them to use (without the installer dialog) how should it be done since we can't have 2 extensions named the same but we need different open commands, is this even possible because the official MSDN shows it only for one app (per installer)?

Thanks in advance

[Daniel]

Hello,

- After the installation when you click the associated file or change the default program the Windows Installer windows launches itself to execute some (related) task, I have tried other apps (external apps) and they don't show the windows installer they just change the default, is there a way to avoid this?

This may happen if a key file ,of a component added under the same feature as your extension component, is missing. In this case if you are launching a file with the above extension (and a key file is missing) then Windows Installer will automatically trigger a repair for the feature containing your extension component. This mechanism is called "self-heeling" or "self-repair".

-If we have two apps in the installation that use the same extension and need to be in the Default Programs list so the user can choose which of them to use (without the installer dialog) how should it be done since we can't have 2 extensions named the same but we need different open commands, is this even possible because the official MSDN shows it only for one app (per installer)?

I'm afraid currently this is not possible. You cannot add the same extension for two application in the same installation project. However, we will add an improvement regarding this in a future version of Advanced Installer. We will notify you when this will be available. Until then, as a workaround you can try to create a merge module containing one of your application and its extension and, then include the merge module in the main installation project.

All the best,
Daniel

[ChristianLA]

This may happen if a key file ,of a component added under the same feature as your extension component, is missing. In this case if you are launching a file with the above extension (and a key file is missing) then Windows Installer will automatically trigger a repair for the feature containing your extension component. This mechanism is called "self-heeling" or "self-repair".

How can this be avoided ?

The process I'm following is:
1. Create a new Program ID
a. Set the description and the ICO file
2. Create a new extension
a. Choose the exe app to launch (main app withing one of my features),
b. No other settings

The extensions show up underneath the component tree for the exe component within that feature

Is there anything else needed?

[Daniel]

Hello,

In order to avoid this you can place the extension in a separate feature which will contain only the extension component. Also, the new created extension feature should not be added as a sub-feature of another feature from "Organization" page.

All the best,
Daniel

[Dan]

Hello,

The improvement to add same extension for both version (32 and 64-bit) of application when using a mixed installation package has been added in version 11.0 of Advanced Installer released on March 13th, 2014.

Best regards,
Dan