I have an app with 2 versions already, one with the original MSI and the later with an MSI, MSPand an MST. Vendor threw some new dll files now after this app is in prod for a long time. How I can and these dll files to this MSI + MSP make a 3rd version of the application that should be able to patch the exisisting versions too? I am using Wise by the way.
0 Comments   [ + ] Show Comments

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.

Answers

0
What tool are you using?
Answered 08/13/2010 by: AngelD
Red Belt

Please log in to comment
0
I'd say maike an AIP of the original MSI, then apply all the MSP patches one after the other.

This should result in a completely patched installation source in the AIP. If the vendor did a decent job authoring the MSI you should be able to update your existing installs with the resulting MSI

PJ
Answered 08/13/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
Whoa! The vendor has just supplied you with new files, not in an MSI or MSP?!? What on earth does he think his clients are going to do when he releases a new version/upgrade/patch? If clients have been left to their own devices, in terms of setting up their own upgrade or patch, he will have no idea what strategy those clients have used. Did they, for example, increment the major version number? Minor? Build? None? What about ProductCode, etc., etc.? What a mess...

Tell this idiot vendor to package up his new files into a new release, packaged properly.
Answered 08/13/2010 by: VBScab
Red Belt

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