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
FOLLOW US
Get the latest news in Application Packaging