/build/static/layout/Breadcrumb_cap_w.png

How to patch some dll files to an eixisng MSI install that also has an MSP in the previous version?

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

Answers (3)

Posted by: AngelD 13 years ago
Red Belt
0
What tool are you using?
Posted by: pjgeutjens 13 years ago
Red Belt
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
Posted by: anonymous_9363 13 years ago
Red Belt
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ