Hi this is my first post, so sorry if I ramble on a bit.
I am after some guidance on how to distribute our application and any updates we will have in the future.
I want to use the partial web deployment as we have some large prerequisites (runtimes and service packs) that need applying originally, but would not be needed again on further updates. Our application also has various optional features that can be put into separate web media blocks quite easily. So no problem here, and I understand this part quite well now.
I would also like to use the patching functionality in IA for minor updates, but I am slightly confused as to how the partial web deployment, and patching integrate over multiple revisions.
Here is a real scenario:
Version 12.00 is released as a full install
version 12.01 is released as a patch
version 12.02 is released as a patch
version 12.03 is released as a patch
version 13.00 is released as a full install/update
version 13.01 is released as a patch
The documentation states that a patch needs to be referenced against a previously built installer source.
My confusion here is which source is required for patching and what stays on the end users machine at any one time as the cached installer source.
If a user has version 12.00 installed and applies the patch for 12.01 this patch would be based on he 12.00 cached installer on the clients machine. I understand this part.
If a user has version 12.01 installed (which is a patched version of 12.00) and applies the patch for 12.02 would the patch need to be based on 12.00 (as this is a full install) or 12.01?
I guess my question is when windows installer applies a patch, does it update the original cached copy of the installer, or create a temporary version of it, apply the msp patch to it, then run that?
My guess at what is happening would as follows, could somebody please correct me if this is wrong
Version 12.00 is released as a full install (cached source is 12.00)
version 12.01 is released as a patch (cached source is 12.00)
version 12.02 is released as a patch (cached source is 12.00)
version 12.03 is released as a patch (cached source is 12.00)
version 13.00 is released as a full update (cached source is updated to 13.00)
version 13.01 is released as a patch (cached source is 13.00)
My other question is about how patching is applied to web media blocks. If all web media blocks changed during a patch, would there be a patch file created for each web media block or is there just one patch file created which would be applied to the entire install?
Hoping somebody can help me in understanding these concepts. By the way I have studied all the whitepapers to do with patching and partial web deployment already.
S
Build / upgrade / patching policy guidance
My understanding after testing with the IA product is that it does not support the MSI 3.0 extended capabilities that allow a client to keep the installer source for the base install (major release) and also for latest patch release. A client will only cache the installer source for the latest installed release. This means that if you are going to embark on a patching policy at all, when you build your installer, it will need to patch against EVERY revision of patch and major release that you want to support an upgrade from. This takes long enough for a single patch diff, but when you compare multiple revisions, you almost need a dedicated build server as it can take several hours or more.
I have opted for the full release each time, but may use the patching functionality for the odd minor release.
Also, it seems that when patching against web media blocks, the patch is a single file that will patch against the entire install irrelevant of which web media block is changed.
Hope this helps
S
I have opted for the full release each time, but may use the patching functionality for the odd minor release.
Also, it seems that when patching against web media blocks, the patch is a single file that will patch against the entire install irrelevant of which web media block is changed.
Hope this helps
S
