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

0 Comments   [ + ] Show 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.


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
Answered 11/09/2007 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
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?
Answered 11/13/2007 by: cjwallace
Orange Belt

Please log in to comment
You could use a custom action to modify the cached MSI.
Is the .exe file versioned or un-versioned?
Answered 11/13/2007 by: AngelD
Red Belt

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