Having got file association working Ok on my msi install, I find that renaming any of the example files delivered by the install that are 'associated' (ie have the associated extension) causes the msi to run again and a copy of the file being renamed is made with its original name. I do not have a clue as to what could cause this. Any ideas greatly appreciated.

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

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

I'm a bit rusty on the WISE Installer Editor, so this may not be the best way but if you go into Setup Editor, click the Tables tab and scroll down to the File table and select that, then you should see all the files in your project listed on the right.

Scroll down the FileName column until you find the file(s) you are interested in.  On the same row, look in the Column marked Component_ and that will tell you which component the file is associated with.

While still in Setup Editor, you can now click the Components tab and find the component you determined earlier from the File table.  Expand that component and click on Files and this should show all the files associated with that component on the right. The keypath file will be indicated by a key icon.

Moving files to a different component (as suggested by a previous poster) should be possible by dragging the file from the list on the right to one of the other components listed on the left .... something I wish I could do in InstallShield, BTW :-)

Regards,

Spartacus

Answered 08/14/2008 by: spartacus
Third Degree Brown Belt

Please log in to comment
0

Many thanks. I am trying to master this.I am very new to msi.
I am working with a wsi created from an existing msi so not sure what the settings are.
Under the component Tab there are lots of WICOMPxxxxxxxx entries. How do I identify a particular file
from the list? I am just working through them to find one at present. Takes ages...
Looking at some component details  I see I have:-
Run Location = Run From Source or Locally
Key path Type = File Key path
File Key Path = <none>
Is this correct?
The help suggest that Key paths are identified with a yellow key over the icon. I cannot see any such keys.
I had the problem files marked as 'vital' , but unticking that has not helped.

Answered 08/14/2008 by: bobdennis
Yellow Belt

Please log in to comment
0

Each component in an MSI file has a "key path" which is an item that is verified by the system and if the item is missing, then the feature that contains the component is repaired.  For example, if the component contains FileA and FileB and FileA is specified as the key path, then a repair will occur if FileA is deleted, but not if FileB is deleted.

It sounds like a repair is being done because each "example file" is set as a key path for the component that it is in.  If you set a different item in the component to be the key path, then it should not repair when the example file is missing.  If the example file is the only item in the component, you may need to move the file to another component.

In Wise Installer Editor, this is done in Setup Editor, Components tab.

Answered 08/13/2008 by: MicrosoftBob
Blue Belt

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