Hi All,
Just need some suggestion. I was ask to make 34 MSI packages of file and folder changes. I am trying to do the following

a) I want to be able to roll back to previous package if need be ( eg If I install package 3 and I need to go back to package 2) what shoud i use MSP?? updates??? MST??? Versioning???

b) I will make changes to file and folders on a weekly bais and just want to know what method would be best.

c) Does anyone know a good rule of thumb for using Updates, versioning, and MSP

Any help or suggestion will greatly be appreciated

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


What you're describing is the new patch functionality provided by MSI 3.0. It has quite a few limitations - see here:


There's a very good (although long) whitepaper on the subject of MSI 3.0 patching here:

Answered 05/13/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
How are you deploying these MSI's?
Answered 05/13/2005 by: Bladerun
Green Belt

Please log in to comment
We are deploying via SMS 2003. What we are really doing is we are updating the company website. so we have the base msi package which we deploy to the IIS servers. Then when there are updates files (dll, ocx, html, )we will deploy it to these servers one every two weeks with the option that if the updates has problem we can always roll back to the previous version.
Next every quarter we will incorporate all the updates into one msi file, deploy to the IIS servers and apply updates every 1 to two weeks.

Just don't know what is the best way to go about doing it. Any help will be greatly appreciated
Answered 05/18/2005 by: UcMerrill
Senior Yellow Belt

Please log in to comment