Installation Version and Assembly Versions when Patching

[kfkyle95]

Previously, we used Wise Installation Studio to build our MSI and MSP patch files. Our process at that point (in summary) was essentially the following :
1. Create release MSI file (keep copy)
2. Copy and rename the *.wsi source project file used to create the released MSI according to the next Hot Fix (Patch) to be distributed.
3. Run their patch preparation utility and update the version number (Product and Upgrade Codes unchanged)
4. Distribute the MSP file to our customers to patch the software

This process resulted in an update to the version number (under Installed Programs) and updates to any assembly files where the version number has been changed according to MSI rules. So, if the assembly had beeen recompiled (date changed) but the version had not been updated, then the MSP technology would not apply that file.


In following the Patching example provided via the IA whitepaper, I've encountered two issues I am trying to resolve :
1.) The product version does not update when the patch is applied, even though the second version of the project that I built I updated this version before building it.

2.) The assemblies are updated regardless of their version. In my case, the date is new, but I specifically did not update the version.


Are there settings I am missing and/or not understanding the IA patching methodologies? The understood the above to be rules specified as part of the MSI/MSP technology.

[giaviv]

Hello,

1.) Patches to do not change the version of the installed product. Patches patch the files that the setup uses but it does not change the version. For that, you will have to issue a new installer.

2.) Could you elaborate on this one? I am not sure I understand the problem.

[kfkyle95]

What we did in the past was considered a minor upgrade of an MSI installation. The media we built and distributed with these were MSP (Patch) files. When those were applied, they updated the version number of the product (i.e. 5.3.1234.000 to 5.3.4567.001) under the Insalled Programs list.


With regard to the assemblies, ours are rebuilt every night, however, we manually version those assemblies if changes are made. In the past, the MSP would only apply an assembly to the target system if their version had changed, therefore, the datetime stamp on those file was not a issue.


I realize we may have to do things different with IA, but I thought these were MSI specific rules and not specific to Wise Installation Studio.

[giaviv]

Hi,

Indeed you will have to make modifications to your design - these are not MSI rules but Wise rules.

Regarding your assemblies, they will be updated if their binary signature is different from the one the installed ones have. InstallAware uses binary patching..

[kfkyle95]

Ok. I am going to research the IA Update Packs as well as this may be preferrable to us in the end.

[giaviv]

Sure, let me know if you have any questions!