Patch 101 - 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!

canuzun
Posts: 15
Joined: Fri Jul 15, 2011 8:25 am
Location: Turkey

Patch 101

Well i need some guidance about patch/upgrade operations. If these questions are not AI related, any direction you can point me will be enough.

Question One;
As i understand in order to have a patch i must have from and to MSI packages. I am currently using Bootstrapper and no MSI packages are created, even if i click "Do not delete extracted MSI and CAB files" i don't see an .msi file. Is file created else where or it is created during installation and not removed?

Question Two;
Even if i make a very minor change and build setup package it needs to be un-installed and re-installed. What is the default approach/Best Practice for this? I mean i use a folder named "Product Name" and inside i have all necessary files. When we release a build, and make modifications after that what should i do? Use another folder "Product Name v.xx" or i should update the previous one? And in order to have the ability for a patch i must keep all of my setup releases, so every .msi file we have published i should keep them, or at least the last one.

Question Three;
I think, any change that requires a new build means a new version. So i must edit version but keep the original Product Code for patching, or a new code for upgrading. How should i decide if this is a patch or upgrade. Any standards such as Bug/Hot Fixes are patches and functinality changes are upgrades?

These questions are probably my lack of knowledge about versioning + release management.

As i have said, even if these issues are not AI questions, any direction you can lead me or any keywords to search will help me a lot. I did read about Creating Patches, Patch Projects and a sample patch project on your guides.

Thank you.

can
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Patch 101

Hi Can,
As i understand in order to have a patch i must have from and to MSI packages. I am currently using Bootstrapper and no MSI packages are created, even if i click "Do not delete extracted MSI and CAB files" i don't see an .msi file. Is file created else where or it is created during installation and not removed?
This is correct, to create a patch you will need the target and upgraded .MSIs. If you are authoring an .EXE installer you can set the .MSI location after build from the Media page -> Bootstrapper tab. The build location can be set from the same page in the Media tab.
If you have the "Include files in EXE" option set, then to extract the .MSI from the .EXE you can use the following bootstrapper command line:

Code: Select all

/extract <path>
This command line extracts the .MSI contained by the .EXE to the specified location. If the path contains spaces you must enclose it in quotes.
Even if i make a very minor change and build setup package it needs to be un-installed and re-installed. What is the default approach/Best Practice for this? I mean i use a folder named "Product Name" and inside i have all necessary files. When we release a build, and make modifications after that what should i do? Use another folder "Product Name v.xx" or i should update the previous one? And in order to have the ability for a patch i must keep all of my setup releases, so every .msi file we have published i should keep them, or at least the last one.
Please keep in mind that patches do not uninstall the old version, but can only be installed if the old version is already present on the target machine. This behavior would be valid in case of a major upgrade. The recommended approach would be to backup all your previous versions source files and projects. To clarify things, here are the steps you can follow in case of a patch:
- back-up of the AIP of the first installation
- open the AIP of the first installation in Advanced Installer
- in the "Product Details" page increase the version (in the "Product Version" field)
- after you select another page you are prompted about changing the Product Code
- in this dialog select "No" because the target and upgraded packages must have the same product code
- update the package (add/modify files, registry keys etc.)
- make sure that nothing is removed
- save and build the project (the target and upgraded packages must have the same name, for example: "test.msi")
- in Advanced Installer create a Patch project
- set the target (old MSI) and the upgraded (updated MSI) packages
- build the project
I think, any change that requires a new build means a new version. So i must edit version but keep the original Product Code for patching, or a new code for upgrading. How should i decide if this is a patch or upgrade. Any standards such as Bug/Hot Fixes are patches and functinality changes are upgrades?
This Microsoft article should clarify this for you. The differences from patches and upgrades are also underlined in this user guide article.

As the patching process requires careful settings, to understand the basic concept, I recommend you first follow our tutorial before implementing the functionality into your main project.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
canuzun
Posts: 15
Joined: Fri Jul 15, 2011 8:25 am
Location: Turkey

Re: Patch 101

Thank you so much for this response. This helped a lot.

Return to “Common Problems”