What does installer look for on Repair option?
Hi Guys,
I have a certain doubt related to components. If i have a particular component that has a some files in it. For instance it has a .dll file; now we know that all files have size version name, language, attributes etc as parameters realted to it.
Now I set a particular file .dll file as a keypath. Later on I remove the file and rename it and provide it to the component manually. In this case does during the trigger of the repair option does the installer recognise the fact that the file was changed as it has a different version, size, attributes, language but has the same file name.
On the contrary what parameters does the installer look for related to the file or is it just the file name.
Thanks a lot. Eagerly awaiting reply
Bye [:)]
I have a certain doubt related to components. If i have a particular component that has a some files in it. For instance it has a .dll file; now we know that all files have size version name, language, attributes etc as parameters realted to it.
Now I set a particular file .dll file as a keypath. Later on I remove the file and rename it and provide it to the component manually. In this case does during the trigger of the repair option does the installer recognise the fact that the file was changed as it has a different version, size, attributes, language but has the same file name.
On the contrary what parameters does the installer look for related to the file or is it just the file name.
Thanks a lot. Eagerly awaiting reply
Bye [:)]
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
turbokitty
17 years ago
I'm sorry I'm not following you.
In your hypothetical situation, you're installing an MSI on a machine. Then you're editting the cached MSI (preserving the product ID) on the machine and changing a DLL inside one component (preserving the component ID)? Then you want to know if the component still gets removed?
Is that correct?
In your hypothetical situation, you're installing an MSI on a machine. Then you're editting the cached MSI (preserving the product ID) on the machine and changing a DLL inside one component (preserving the component ID)? Then you want to know if the component still gets removed?
Is that correct?
Posted by:
India_Repackaging
17 years ago
Hi,
I am afraid you got me all wrong. I apologise that I should have been more specific.
I wanted to know that I have a MSI and it has got a component which has a file key path. I install the package. Now I replace that file with a file with a different version, size, language,etc but retaining the same name. Then when I repair the application by deleting that file, it looks for the file. So in this case does it recognise the file by only the file name and performs repair or does it recognise the file with different version and size and prompts that the file is missing? So what parameter of the file does it look for?
I am afraid you got me all wrong. I apologise that I should have been more specific.
I wanted to know that I have a MSI and it has got a component which has a file key path. I install the package. Now I replace that file with a file with a different version, size, language,etc but retaining the same name. Then when I repair the application by deleting that file, it looks for the file. So in this case does it recognise the file by only the file name and performs repair or does it recognise the file with different version and size and prompts that the file is missing? So what parameter of the file does it look for?
Posted by:
turbokitty
17 years ago
Ah, I see. As far as I know, it will only check the file version. If the version on the box is older than the one you set in the MSI, it will repair with the new version. Otherwise, it leaves the file intact.
That's my understanding, but I'm open to being corrected.
That's my understanding, but I'm open to being corrected.
Posted by:
turbokitty
17 years ago
There's also the trouble of non-versioned files. If the files aren't versioned, then MSI uses the file's create (installed) date and the file's modified date and compares them (it doesn't look at the file inside the MSI for a date).
If the exisiting file on the box has a modified date that's newer than the create date, it doesn't touch it.
Of course, that's only true if you didn't set the component in the MSI to never overwrite.
Clear as mud!
If the exisiting file on the box has a modified date that's newer than the create date, it doesn't touch it.
Of course, that's only true if you didn't set the component in the MSI to never overwrite.
Clear as mud!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.