Trying to understand requirements for patch files - Advanced Installer Community
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Trying to understand requirements for patch files

Hi,
I understood that we couldn't really use MSP patching for our typical installation scenarios because we release patches monthly to our clients and if a client skipped one patch (say version v14.4) and jumped from v14.3 directly to v14.5 then they would miss out on the diffs that were delivered between v14.3 and v14.4. But we are wondering if there is an alternative methodology available.

For example, can a patch be created to do a diff from some anchored, initial version, say v15.0. Let's say the client installs v15.0 using our Full Setup as their first-ever install, would it be possible for us to create future patches like v15.1, 15.2, 15.3 etc. so that those patches are created as being the diffs that exist from the 15.0 anchored version? This way if a client jumps from 15.0 to 15.3 (for example) they will get all of the changes made to our product in those 3 interim releases, in the same way that they would have gone if they had applied all 3 interim patches?

Also, regarding patching: can MSP packages be delivered & installed using the native Updater technology that is built into AI? And does it benefit from all of the same features as the full Setup does, namely: download and install for limited user (no UAC), etc.

Thanks,
Kevin
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Trying to understand requirements for patch files

Hello Kevin,
I understood that we couldn't really use MSP patching for our typical installation scenarios because we release patches monthly to our clients and if a client skipped one patch (say version v14.4) and jumped from v14.3 directly to v14.5 then they would miss out on the diffs that were delivered between v14.3 and v14.4. But we are wondering if there is an alternative methodology available.

For example, can a patch be created to do a diff from some anchored, initial version, say v15.0. Let's say the client installs v15.0 using our Full Setup as their first-ever install, would it be possible for us to create future patches like v15.1, 15.2, 15.3 etc. so that those patches are created as being the diffs that exist from the 15.0 anchored version? This way if a client jumps from 15.0 to 15.3 (for example) they will get all of the changes made to our product in those 3 interim releases, in the same way that they would have gone if they had applied all 3 interim patches?
Yes, this can be done. Just add all of your previous version as target images when creating a patch. In this way the patch could be applied against all versions added as target images on "Images" page from your patch project.

For example, if you want that patch v15.3 could be installed against any of the following versions: v15.0, v15.1 and v15.2, then the hierarchy from "Images" page of your patch project should look like this:
Family
- v15.3 ( upgraded )
--- v15.0 ( target )
--- v15.1 ( target )
--- v15.2 ( target )

Also, please be aware that you fulfill all patch requirements when creating patches.
Also, regarding patching: can MSP packages be delivered & installed using the native Updater technology that is built into AI? And does it benefit from all of the same features as the full Setup does, namely: download and install for limited user (no UAC), etc.
Yes, just create an updates configuration file for your patch package as it is described in our "Manage a patch" section of the updater article.

If you have any questions just let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Re: Trying to understand requirements for patch files

Hi,
Thanks for the reply. This sounds promising.

The way we work is to we typically (99% of the time) build on to existing functionality so that if v15.0 contains Features A, B & C, and then version 15.1 adds Feature D (so this version contains features A through D), and 15.2 adds Feature E (so this version contains features A through E); almost never does a maintenance release remove a prior feature.

So, if we were to require that the initial install by our clients be v15.0 and then what if we only offered the most recent maintenance release as a patch, this month it might be, v15.3, and next month it might be v15.4 (or perhaps it would be v15.3.1), then could that be done in the AI "Images" to where I only have to link back to the v15.0 image as the base install and then the upgrade (MSP) would be the diffs between v15.0 and v15.3. I am trying to avoid having to add the interim releases as "Targets" every time that we build a maintenance release, so that this project remains as stable as possible over time.

Thanks,
Kevin
Last edited by kjullion on Fri Nov 14, 2014 4:59 pm, edited 1 time in total.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Trying to understand requirements for patch files

Hello Kevin,

If you will add only a target image (e.g.v15.0) under your upgraded image (v15.3), then please keep in mind that the currently built patch (v15.3) could be applied only against v15.0 of your product.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Re: Trying to understand requirements for patch files

Hi,
Thanks for your reply.

Additional questions about patch projects. It appears that the Patch type project requires the target and upgraded projects to be saved as "Single MSI (resources inside)" because on the patch projects Images page the "General" section of the "Upgraded Image Properties" and the "Target Image Properties" only says "MSI package", and doesn't seem to want to allow "EXE" type packages. Is that a correct assumption of mine?

If that is the case, are there any major hurdles or considerations that I should know about when switching back to MSI, the reason I'm a little hesitant is that I am only now experimenting with patch projects and if it can't / doesn't do what we want then we might want to go back to what we have now which is "Single EXE setup (resources inside)", and I do want to make sure I don't mess up what looks to be a pretty solid installer package using that method.

Thanks,
Kevin
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Trying to understand requirements for patch files

Hello Kevin,

No, there is not mandatory to build your target and upgraded setups as MSI packages. You can also build them as EXE packages with resources inside and, then use the EXE /extract command line to extract the MSI from the EXE. Then, you should just create a patch between the extracted MSI packages from your target and upgraded setups.

If you have any question just let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”