PMartin
Posts: 2
Joined: Wed Feb 24, 2010 9:14 pm

Advice for new user - Project Setup/best practice

Hello,
We're evaluating using Advanced Installer to replace an ad-hoc install/update methodology we've been using for a desktop product.

It seems that getting a fresh install up and running, with all our special folder requirements et al is quite simple, and using the patch tool to diff between two MSIs works wonderfully. The questions I'm running into are based on efficiency and methodology.

Our product has many separate pieces, some of which do not require a recompile of the main binaries (things like XML config files, external data files, etc). With our current ad-hoc solution, I can push out updates for just this one portion of our app. I'm struggling to find the *best* way to do this using Windows Installer/Advanced Installer. Here's the rub - we don't want the users to be able to de-select items. we want to require them to update all-or-none. I could still see this working with the patch created from two different MSIs, but since we're not rebuilding the main binary the product version would it be necessary to rebuild to simply increment the version number? (assuming I base the product version on the main binary build version).

I'm a little unclear on making patches - from the looks of things, I have to build a base MSI, and every update is a patch off of that - otherwise a user who skips a version in their updates would have to download patch 1, install it, then download patch 2 and install that - if I'm mistaken please advise.

Tying into the previous question - I'd also like to know if there is any best practice when it comes to a slightly different situation, such as 3rd party components that must be linked into the main app, but do not change as frequently as the main app. For instance - a vendor supplied UI component, might stay unchanged for a year, while our app is patched 3 times. Is it best to just include the vendor component(s) in the main MSI (where they'll contine to be distributed in patch after patch) or would that be better served as a prerequisite, hosted in a separate installer (which is only an option for us if we can force the user to take that update along with the update to our binaries).

I know that's a lot of questions to drop, sorry for so many, but we're excited to find an app like this that can help us move to a more stable install/update solution than what we're currently using - thanks for your help.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Advice for new user - Project Setup/best practice

Hi Martin and welcome to Advanced Installer Forums,

It's no problem at all, we're here to help.

Here's how patches are used most of the time:

Code: Select all

- version 1.0 deployed with full msi installer
  - version 1.1 - patches 1.0 to 1.1  
  - version 1.2 - patches 1.0 to 1.2 and 1.1 to 1.2 
  - version 1.3 - patches 1.0 to 1.3, 1.1 to 1.3, 1.2 to 1.3
- version 2.0 deployed with full msi installer
  - version 2.1 - patches 2.0 to 2.1
 
************ and so on ************
As you can see, a patch can be set up to have multiple targets, meaning it can upgrade multiple versions.
In the example above, patch 1.3 can update a Product with version 1.0 or 1.1 or 1.2. But the 2.1 patch won't be able to update a product v1.1. The user would have to download the full 2.0 installer and then apply the 2.1 patch. That is unless you set up 2.1 to update 1.0, 1.1, 1.2, 1.3 and 2.0. But that would get messy as you release more and more updates, the patches would have to be set up to be able to update all previous versions, and you'd eventually be better off just releasing major upgrades with full msi installers.
I could still see this working with the patch created from two different MSIs, but since we're not rebuilding the main binary the product version would it be necessary to rebuild to simply increment the version number? (assuming I base the product version on the main binary build version).
Well it would make sense to keep the main exe version and the installer version the same if your product was only made from one piece. But I doubt it would be a good practice to increment your main app's version number if it did not change. After all, that's what versions are for, to indicate change. Incrementing your app's version number would mean it would be included in the patch. That's how patches work. And this is what you're probably trying to avoid, reinstalling unchanged parts of your app.
I would suggest you increment the installer's version number but leave your main app's version number intact.

Regarding 3rd party components, I might be wrong but most 3rd party vendors require redistribution of their components to be made using their installers. Repackaging their components might not be a good idea.
They usually offer different methods for redistribution, like merge modules or installers.

If the 3rd party uses merge modules, they can be incorporated into the patch painlessly. However should they use installers, you would only be able to update the component when updating your app using a full installer.

Packaging 3rd party installers along with your own installer is not directly supported by older versions of Windows Installer (before chained packages were available). Therefore we implement this functionality by wrapping your msi installer and the 3rd party installer into a single .exe installer which will both install the 3rd party component and your product. You can then mark the prerequisite (the 3rd party component) as mandatory. You can check our guide on Prerequisites.

You can learn about the subjects discussed in this thread by searching through our guide. We cover various related topics there. You might also want to follow our tutorials, you will find them of great use.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
basavaraj.kn
Posts: 3
Joined: Tue Jan 21, 2014 12:17 pm

Not copying some files(.exe) while installing upgraded msi f

Hi,

I am facing a problem while reinstalling upgraded msi file.

First I installed a version 3.0 application(.msi file) and then I tried to upgrade with 3.1 application, while installing 3.1 app, it uninstalled 3.0 version app successfully and then installed 3.1 version, but it failed to copy some of the important exe files.

After installation process completed, it opens "C:\Windows\system32" folder automatically in the windows 7/8 OS.

I would request you to assist me on this.

Thanks,
Basavaraj
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Advice for new user - Project Setup/best practice

Hi Basavaraj and welcome to Advanced Installer forums,

I'm not sure why you encountered this behavior.

In order to have a better view about this, can you please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate them?

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
basavaraj.kn
Posts: 3
Joined: Tue Jan 21, 2014 12:17 pm

Re: Advice for new user - Project Setup/best practice

Hi Dan,

I sent a email from my office email account with all inputs that you asked.

Thanks,
Basavaraj
basavaraj.kn
Posts: 3
Joined: Tue Jan 21, 2014 12:17 pm

Re: Advice for new user - Project Setup/best practice

Hi Dan,

Did you received my mail?
Please conform.

Thanks,
Basavaraj
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Advice for new user - Project Setup/best practice

Hi Basavaraj,

It seems that Windows Installer fails to detect correct the version of the related files. In this case, you can enable the Always overwrite existing file option from the Operations tab of the Edit File Properties dialog. Using this option, the file from your package will overwrite any similar file already present on the target computer.

If you have other questions, please let us know.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”