Patching issue
Good day all,
I have an app that is developed by one of our vendors that I need to create a patch for. The app has had two of the main EXE files changed to correct a few minor bugs. The files have internal version numbers from the development tool embedded into them. When I create my upgrade after running upgrade sync, the MSP file does nto replace or modify these two files even though they are the only two that are different between the two packages. I read through the msgs about the MSIFileHash and thought that this might be the answer but I then saw that this is for unversioned files. Is there something else I am missing?
I also tried adding the upgrade data to the new package and ran into the same results.
Jimm
I have an app that is developed by one of our vendors that I need to create a patch for. The app has had two of the main EXE files changed to correct a few minor bugs. The files have internal version numbers from the development tool embedded into them. When I create my upgrade after running upgrade sync, the MSP file does nto replace or modify these two files even though they are the only two that are different between the two packages. I read through the msgs about the MSIFileHash and thought that this might be the answer but I then saw that this is for unversioned files. Is there something else I am missing?
I also tried adding the upgrade data to the new package and ran into the same results.
Jimm
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
What does verbose logging tell you, in terms of the choices made when comparing file versions?
Posted by:
jmcfadyen
15 years ago
ensure you have the REINSTALLMODE property set correctly on your patch.
have a crack at msiexec /p <path to patch> REINSTALLMODE=omus or vomus whichever suits your needs better.
ensure the assemblies are versions higher than previous for that to work.
alternatively if you have unversioned files you can look at the use of companion files.
have a crack at msiexec /p <path to patch> REINSTALLMODE=omus or vomus whichever suits your needs better.
ensure the assemblies are versions higher than previous for that to work.
alternatively if you have unversioned files you can look at the use of companion files.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
