Good morning Appdeploy,

how do you ussually handle file association. Example:
1. MSI installation doesnot maky any file association.
2. So immediately after install you can not open e.g. .xxx by double click.
3. Also after restart is it still without.xxx file association.
4. File .xxx association is made by running the application. And is done onli for HKCU

So how do you ussually handle file association to manage it as you want to.

I am suggesting make file associatio via MSI into HKLM(this solve the first click on .xxx) for all users or any other way?

thank you
xxMBxx
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
You already posted on this subject. Please don't repeat-post, just be patient.
Answered 12/02/2009 by: VBScab
Red Belt

Please log in to comment
0
I just dont wont to block the freemind thinking by orienting into the subject as I am looking on it.
Answered 12/02/2009 by: xxMBxx
Orange Belt

Please log in to comment
0
Hi

You can very well handle this using File Association option in the Installation Expert. You need to specified the extension and its associated exe file.

for example : doc files winword.exe

Below is the help document extracted from WSP.
Adding File Associations
Use the File Associations page to associate file extensions with executables to determine which application to start when the end user double-clicks a file with a certain extension. You can associate file extensions with any executable file in an installation. File associations are a type of advertising and are stored in the registry.
To add a file association
1. Do one of the following:
nSelect Installation Expert > File Associations page.
a. From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.)
Items that you add to a feature are installed on the destination computer only if the feature is installed. Items that you add to a condition are installed only if the feature is installed and the condition is true.
b. Click Add at the right of the page and select New.
nIn Setup Editor, on the Components or Features tab, right-click a component or feature and select New > File Association.
The File Association Details dialog box appears.
2. On the Extension Details tab, select the executable to use for the extension, type an extension, and enter the program ID for the executable.
See Determining Extension Settings.
3. (Optional.) On the Command Verbs tab, click Add, and on the Verb Details dialog box that appears, set the actions that will be available when the end user right-clicks an executable with this extension in Windows Explorer.
See Adding Command Verbs.
4. (Optional.) On the MIME Types tab, mark Show All and mark check boxes to select the MIME types to associate with this extension.
See Selecting MIME Types.
5. Click OK.
The file association appears. To edit it, double-click its name. To delete it, use the right-click menu.
In Setup Editor, a new branch of folders is created under the Advertising icon to show the application folder, the Extensions folder, and the ProgId folder.
To import a file association
1. Select Installation Expert > File Associations page.
2. From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.)
3. Click Add at the right of the File Associations page and select Import.
The Import File Association dialog box appears.
4. Click Browse to select the executable to use for the extension. You can only select executables that you have already added to the installation.
5. From Extension, select the extension to use. This list shows all available extensions on your computer.
6. Click OK.
All relevant information for the extension you select is imported into the Extension Details, Command Verbs, and MIME Types tabs. To edit those tabs, double-click the file association name.
Answered 12/02/2009 by: WSPPackager
Senior Purple Belt

Please log in to comment
0
...all of which would be fine IF the OP were using Wise Package Studio. If you read his other post (which led to my admonishment) you'd see that he's using InstallShield.

@MB, now you see why repeat-posting is a bad idea.
Answered 12/02/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity