Force Repair if another app repairs
Hi guys. I hope someone can help.
Ok i have two different packages lets say package A and Package B
In package A it has a .exe that is say version 1 and in package B it has the same .exe that is version 2.
Package B when installs over writes package A .exe with the version and file size we want and everything is happy days.
Now if package A does a self repair or the user does a repair it will put .exe with version 1 back down on to the machine.
So is there a way if this happens that we could cause package B to do a repair to put back the .exe version we want? The .exe in package B is set as a key file.
Any ideas welcome and thanks in advance
Craig
Ok i have two different packages lets say package A and Package B
In package A it has a .exe that is say version 1 and in package B it has the same .exe that is version 2.
Package B when installs over writes package A .exe with the version and file size we want and everything is happy days.
Now if package A does a self repair or the user does a repair it will put .exe with version 1 back down on to the machine.
So is there a way if this happens that we could cause package B to do a repair to put back the .exe version we want? The .exe in package B is set as a key file.
Any ideas welcome and thanks in advance
Craig
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
michaelnowell
17 years ago
Within package A edit the component that the .exe belongs to and make the .exe file the keypath. Then set the component to 'never overwrite if key path exists'.
You might also want to look at the value of the property of REINSTALLMODE within package A to see if it is set to overwrite the Package B file.http://msdn2.microsoft.com/en-us/library/aa371182.aspx
You might also want to look at the value of the property of REINSTALLMODE within package A to see if it is set to overwrite the Package B file.http://msdn2.microsoft.com/en-us/library/aa371182.aspx
Posted by:
cjwallace
17 years ago
Thanks for the reply mate.
Ok small issue with your solution. Pakage A is already installed on all workstations so i cant edit the .msi. Can you think of any other way we can do it?
Ok small issue with your solution. Pakage A is already installed on all workstations so i cant edit the .msi. Can you think of any other way we can do it?
Posted by:
AngelD
17 years ago
You could use a custom action to modify the cached MSI.
Is the .exe file versioned or un-versioned?
Is the .exe file versioned or un-versioned?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.