Problem Creating File Associations, Corrupt Registry

[Sheri_Steeves]

Hello,

I am trying to create a file association with my install.

I've set the file type along with a default icon to use for the document:

FileAssoc1.png (7.89 KiB) Viewed 6708 times

I've set the file extension:

FileAssoc2.png (4.95 KiB) Viewed 6708 times

And I've added my open command:

FileAssoc3.png (8.44 KiB) Viewed 6708 times

After I run my install, creating one of my files in my program will show the correct icon, but if I double-click this file to open it, I get the error message "There was a problem sending the command to the program". The file is opened by my application in the background.

When comparing the same file association for a previous version of the product installed with a different installer, I noticed some missing registry keys, mainly default "open" keys. If I added them in manually, it started to work properly.

I tried to get around this issue by creating the registry keys myself using the registry panel in the design view. To start, I had problems entering in the keys manually, getting the error "0| is not a valid integer".
I imported the registry keys from a .reg file and still got the error but I could ignore it. Now I still get the error and the registry panel won't display. I commented out the registry settings in the msi script but the panel still will not display.

I have two questions:

1. How do I add a file association with a custom icon and not get that error? I have used the file association in the past with another install (with a previous version of InstallAware) that did not use a custom icon and it worked correctly.
2. How do I fix my script so that I get back into the registry panel?

Thanks,

Sheri

[Sheri_Steeves]

Ok, I managed to fix my script by deleting the registry keys from the msi script panel. Still working on the other issue.

[FrancescoT]

Dear Sheri,

the simplest way it is to import the File Association directly, obviously if this is already defined with your development machine.
To import a file Association, select IMPORT instead of to DEFINE a new one ... you can modify it later if required.

Regarding the parameters required, these depend on the "command / verb" accepted by your application.

As Icon you can use one of those embedded with your EXE. In this case you must verify if the one you want to use is effectively available and you need to know the correct Icon index. Alternatively you can also use a separate Icon file for this purpose.

Hope this helps you.

Regards

[Sheri_Steeves]

Francesco,

I did manage to get the file association working; the problem turned out to be the extra(optional) DDE command "open" I was specifying as on the Shell verbs tab. Once I removed that then double-clicking the file opened correctly with no error.

Thanks,

Sheri

[FrancescoT]

I'm happy you solved!

Regards