Re: Follow Up: MSI Upgrade
Jeffrey Altman <[email protected]>
| Newsgroups | gmane.comp.file-systems.openafs.devel.win32 |
|---|---|
| Organization | No Longer Affiliated with Columbia University in the City of New York |
| Message-ID | <[email protected]> |
Robert E. Smith jr. wrote: > Hi, > > > > I think I understand now what needs to be added to the MSI. Why not add > some of the version numbers for previous packages, instead of admins > having to go through the transform process each time? > > > > Sorry for any confusion. > > > > Bob > Now I am confused. The reason CMU has to apply a transform for each release is to add the customizations that are required for the CMU installation. My understanding is that an MSI will not uninstall a previous version unless the deployment either by GPO or msiexec.exe specifically instructs the installer engine to do so. From msiexec.exe this is done by specifying msiexec.exe /fvomus <msi-name> The package entries in the MSI leave the version number range open so that you can successfully upgrade and downgrade. We will not change the Product ID for the MSI until such time as there is a significant change in the file hierarchy. Jeffrey Altman P.S. - I'm sure Asanka will correct me if I have gotten something wrong.
smime.p7s
(application/x-pkcs7-signature, 3.2 KB) - not displayed