How to create and maintain Patch Installers. - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

IainC
Posts: 6
Joined: Thu Mar 14, 2013 12:32 pm

How to create and maintain Patch Installers.

We have recently transitioned from Installshield to Advanced Installer and are generally quite pleased with the new software. However, the elephant stomping around the room is the patch install technology which seems to leave us with a real problem.

Our software is a typical application where we have a functional point release (e.g 8.1, 8.2, 8.3,...) and several interim maintenance or service pack releases (8.1 SP1, 8.1 SP2, etc..). Our assumption is that each point release is a full install and forms a new baseline for the subsequent service pack patch installs. Our options here seem to be :

1) Create a patch against the base copy for each service pack release.
2) Create a separate installer with only the modified directories at each service pack release.

It seems we cannot use patch installers with watch directories as they use reference id's rather than filenames. Attempting to manually check each file in the directories on each patch build is time-consuming, dangerous and bound to go wrong.
On the other hand, If we roll our own second installer it looks as though we will have problems with repairs/un-installs and also with product grouping, versioning and build numbers.

I'm sure we are missing something here. Could somebody please advise :

- If I build a Service Pack 5 patch (8.0 SP5) by diffing against our baseline release (8.0 SP0) will that install service all users with interim service pack releases (8.0 SP0 users, SP1 users, SP2 users, SP3 users, SP4 users) ? Logically, it could as the file changes will be incremental over SP releases. If not, am I right in saying that I would need to build and maintain 10 different patch installs to migrate users from 8.0 SPx up to 8.0 SP5 ?
- How can I create a patch install with watched directories ? If I can't, some way to manage this that doesn't involve manual comparison of thousands of files ?
- How is everyone else doing this ? Surely this is a standard requirement in application software.
- Is there a wiki or a procedure I can reference ?

Many thanks.
Iain.
IainC
Posts: 6
Joined: Thu Mar 14, 2013 12:32 pm

Re: How to create maintainable Patch Installers.

title typo.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: How to create and maintain Patch Installers.

Hello and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.
- If I build a Service Pack 5 patch (8.0 SP5) by diffing against our baseline release (8.0 SP0) will that install service all users with interim service pack releases (8.0 SP0 users, SP1 users, SP2 users, SP3 users, SP4 users) ? Logically, it could as the file changes will be incremental over SP releases. If not, am I right in saying that I would need to build and maintain 10 different patch installs to migrate users from 8.0 SPx up to 8.0 SP5 ?
In order to achieve what you want you should configure your 8.0 SP5 patch to be applied to more installation targets. So, when creating the 8.0 SP5 patch project, on "Images" page, you can add more targets (i.e. 8.0, 8.0 SP0, 8.0 SP1, ...) for your upgraded msi using the "New Target..." context menu option.
- How can I create a patch install with watched directories ? If I can't, some way to manage this that doesn't involve manual comparison of thousands of files ?
I'm afraid I don't fully understand what you mean. Can you give us more details about this? Please keep in mind that you should decide when to create a new version of your product (deployed as a patch).
- How is everyone else doing this ? Surely this is a standard requirement in application software.
- Is there a wiki or a procedure I can reference ?
In order to get a starting point you can follow our "Patch Authoring" tutorial. Also, when creating patches you should make sure they respect the patch rules.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
IainC
Posts: 6
Joined: Thu Mar 14, 2013 12:32 pm

Re: How to create and maintain Patch Installers.

Thanks for your reply.

By 'watched directories' I mean 'synchronised folders'.

With thousands of files in play it's important that we not lose this in the patch. Is there any way to create a patch installer with synchronised folders (assuming no file rename / deletion).

Thanks,
Iain.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: How to create and maintain Patch Installers.

Hi Iain,

One of the most important rules in patch creating imposed by Windows Installer is to maintain the same component GUID for the files you already have in your project.
Our synchronization support maintains the GUIDs, but it can change them if you accidentally open/build the project and one or more of the files included int he synchronized folder are missing.
This is why we do not recommend it.

If you are VERY careful you can use synchronization in projects for which you will create patches. You must be careful to never open/build the project if one of the files that was included in the package
is missing. You can check this by making a diff between the aip files of the two versions and also you can check the build log from Advanced Installer when building the patch project.
In that build log you will see warnings/errors if GUID mismatches are identified.

Also, if in one of the patches you want to remove a file, you can do that by deleting it. But you also must add an entry for the file removed in the table RemoveFile as documented by Microsoft, to inform the patch about its removal.

Best regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
IainC
Posts: 6
Joined: Thu Mar 14, 2013 12:32 pm

Re: How to create and maintain Patch Installers.

Our synchronization support maintains the GUIDs, but it can change them if you accidentally open/build the project and one or more of the files included int he synchronized folder are missing.
This is why we do not recommend it.
Understood. However, I'd like to know whether the re-mapping of GUID's where a file is missing is done by Advanced installer or Windows Installer. I can't really see why you need to throw away the existing mappings and start again. If this is done by Advanced Installer can I ask that some attention is given to the issue as a feature request.

It's a very serious issue for us (and surely for everybody else !!) in build quality assurance. From this discussion I gather my options are :

1) Manually manage folders. Thousands and thousands of files so bound to go wrong. Not an option.
2) Use synchronised folders but it will all go wrong if a build file is removed. Not good.
3) Abandon patches and force users to pull > 400M on each service pack. Not good.

None of the above is really suitable for large scale deployment of a big application.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: How to create and maintain Patch Installers.

Hello,
Understood. However, I'd like to know whether the re-mapping of GUID's where a file is missing is done by Advanced installer or Windows Installer. I can't really see why you need to throw away the existing mappings and start again. If this is done by Advanced Installer can I ask that some attention is given to the issue as a feature request.
The components associated GUIDs are generated by Advanced Installer. Also, please note this is the normal behavior and it cannot be changed. When a file is missing it will be removed within your installation project (at build time or when a refresh operation is triggered), and its associated component will be removed too. Therefore, when the missing file will be added back into your project it will be associated with a new component (having a new generated GUID).

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
IainC
Posts: 6
Joined: Thu Mar 14, 2013 12:32 pm

Re: How to create and maintain Patch Installers.

The components associated GUIDs are generated by Advanced Installer. Also, please note this is the normal behavior and it cannot be changed. When a file is missing it will be removed within your installation project (at build time or when a refresh operation is triggered), and its associated component will be removed too. Therefore, when the missing file will be added back into your project it will be associated with a new component (having a new generated GUID).
Yes - I understand that and makes total sense.

What I would like to clarify is what happens to all of the other component GUID's at that point. It is one thing to remove/regenerate a GUID for a missing /added component and entirely another to create new GUID's for *all* of the components when this happens.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: How to create and maintain Patch Installers.

Hello,

Please keep in mind that the rest of your component will not be affected. If their resource files will not be removed, then the rest of your components GUIDs remain unchanged.

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

Return to “Common Problems”