Hi there!

I have got a MSI-package from the application developer of a software and they are also sending a exe-file to "update some files". I have also got a reg-file from them to update "some things in the registry".

Whats best practice?

Shall I:
1) Import the changed files and setting into a MST and CAB?
2) Rebuild the MSI with the changed files?
3) Make a new snapshot with everything?
4) Keep the MSI as it is and make a Patch for the changes?

Any other suggestions?


0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Hi Jonas,
if you know how to, change the MSI, either via MST or directly.
But make sure, that the files are full versions and not just patches.
You could install the app and capture the changes which the additional files are causing.
Then open the captured MSI and the original MSI and work the the extra stuff into it.
Hope this gives you some ideas.
Regards, Nick
Answered 02/26/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
If you already have the MSI package installed on your computers then depending on your distribution tool you could:
remove old and install new
reinstall an updated MSI
updated through MSP

Why couldn't the vendor give you a new MSI or MSP if they already have handed you one MSI already?
Answered 02/26/2007 by: AngelD
Red Belt

Please log in to comment
Thanks for your reply.

I have a older version of the application installed on the clients and now I need to update it to a new version.
And they have maked this "patch" for the new version.

It was a setup.exe that extracted a MSI-package, so I guess the reason for that they have not maked a new MSI or a MSP is that they just can't handle it.

Answered 03/01/2007 by: jonasm
Blue Belt

Please log in to comment
So if they can't manage to create patches but you may not know if they do in the future and as you havn't told which distribution tool you uses this is one way to go:
Update the (a new) MSI, change the ProductCode & PackageCode and then add the old MSI to the Upgrade table.

If they release a future patch for their old MSI then do the same but patch the vendor (admin install) MSI before deploying.
Answered 03/01/2007 by: AngelD
Red Belt

Please log in to comment