Build updateable setups with each CI-Build - Advanced Installer Community
SeniorTete
Posts: 3
Joined: Wed May 13, 2015 2:55 pm

Build updateable setups with each CI-Build

Hallo,

with each checkin we build all the code and directly after this we build a new setup with the current binaries.
The problem is the update-behavior of the msi-package. I cant update without uninstal the previous installed version.
Is it really necessary to edit the aip-File with each build? Is there any way to do this automaticly only by the file-version of the binaries?

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

Re: Build updateable setups with each CI-Build

Hi Rico and welcome to our forums,

There is option for this. If you have an EXE as output (maybe only for testing, in a separate build, if you usually deploy and MSI) you can go to Builds page (old name "Media")
and enable the option Uninstall a package with the same version. Remember, the option is visible only if you have EXE package set as output for your build.

The EXE bootstrapper is required because of the way Windows Installer works. Basically the situation you encounter should never happen to your users, because every time
you give them an update you increase the version number. But MSFT has never thought about a method to make testing easier of the same package, this is where our solution
is here to help you.

Also, it should be noted that testing repeatedly the same package on the same might give you unexpected installation/application runtime behaviors. Usually virtual machines
are recommended for testing the packages, this way you can restore the machines to the same stage after each test, so previous tests do not affect in any way the outcome
of the latest one, and also this way you avoid the main problem we're discussing here :)

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”