Greetings,
We are new to MSI installer technology and need a little direction. We are using IS to create MSI’s. Our product suite consists of about 20 installs. I have read and understand (I think) the rules for upgrades posted here (http://msdn.microsof...y/aa370859.aspx) as it pertains to the install. What are best practices for bumping the version and product code based upon the functionality of the system not the install itself? Our install versions 1.2.3 (major.minor.build) match the version of our suite of products. We only bump minor version when our suite version becomes incompatible with a previous version. By incompatible I mean the database changes or a published interface (web service) changes.
What are some best practices to for taking in account functional system changes when versioning installs?
Thanks in advance,
Steve
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Best Practices for Upgrades
Started by
lomicka
, May 21 2010 14:53
2 replies to this topic
VBScab
-
- Full Members
- 436 posts
Posted 21 May 2010 - 15:37
I would think most people match the package version to the main product version. I imagine it would be a management/administrative nightmare otherwise.
- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. Please appreciate the time I give here and don't send me personal emails.
- Try using http://www.google.com before posting.
- I answer questions only via forums. Please appreciate the time I give here and don't send me personal emails.
lomicka
-
- Full Members
- 2 posts
Posted 21 May 2010 - 16:23
VBScab -> Thank you for your reply. That is what we kinda came up with. Just looking for reassurances we are doing it correctly….