Installing New Application Version - 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!

bkandler
Posts: 4
Joined: Fri Dec 24, 2010 10:45 pm
Location: Arroyo Grande, California
Contact: Website

Installing New Application Version

I'm in the midst of evaluating Advanced Installer as a replacement for Install Builder; a product I've been happy with for several years. Unfortunately, that product is now dead and I must find a new way. I've managed to create an install package using Advanced Installer that functions on both 32 and 64 bit machines and so most of my needs are met with your product.

But my customers need to be able to install upgrades or plugins to my software and the upgrades/plugins should go into the same locations as the original install. I see where your program sets up to install into the same location or I could set up a custom action to search for the install directory and do that part myself. I don't need anything fancy here. I already handle automatic updates within my software and there is no need/reason for having multiple versions installed.

What I'm not getting is the ability to do this without uninstalling the prior version. It's not rocket science. We're just trying to replace 1 or 2 files in the installation. It's much the same situation a user will face when he/she installs but the program doesn't work. Most people attempt to redo the install and don't useally uninstall first. The user should see a dialog that allows him to repair or refresh the installation with no other action required. Or, if it's a new version, just install without a whimper.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Installing New Application Version

Hi,
But my customers need to be able to install upgrades or plugins to my software and the upgrades/plugins should go into the same locations as the original install.
Updates automatically use the original install location when using the default configuration. Plugins should use separate projects so their installer don't conflict with the original product. The main installation can write it's installation folder (APPDIR property) in the registry. The plugins can then use a search to retrieve it and a Property set with formatted custom action to set installation folder.
What I'm not getting is the ability to do this without uninstalling the prior version.
Windows Installer has two types of automatic upgrades:
- major upgrades in which the old version is uninstalled before or after the new install
- minor upgrades which are patches

If you are updating only a couple of files, we recommend using patches.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
bkandler
Posts: 4
Joined: Fri Dec 24, 2010 10:45 pm
Location: Arroyo Grande, California
Contact: Website

Re: Installing New Application Version

Setting the install folder in the registry during the base install works for new customers, but not the 2000+ that already have the program installed. For that situation I need to search for the orginal executable.

I'll examine the Patch function.
bkandler
Posts: 4
Joined: Fri Dec 24, 2010 10:45 pm
Location: Arroyo Grande, California
Contact: Website

Re: Installing New Application Version

Using the Patch function looks like a real cludge from my perspective. I certainly hope that the instructions to use command line switches only apply to me (the developer), as my customers are not particularly computer literate.

Since a true 'patch' is an incremental change, what does the installer do about user attempts to apply the same upgrade package a second time. That's something they are apt to try when something doesn't work.

The requirement to have the patch package have the same name as the original install complicates user downloads of the packages a bit, though I ought to be able to cause a rename of the downloaded item.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Installing New Application Version

Hi,
I certainly hope that the instructions to use command line switches only apply to me (the developer), as my customers are not particularly computer literate.
What command line switches are you referring to? Patch creation or deployment do not use command lines.
what does the installer do about user attempts to apply the same upgrade package a second time.
It repairs the installation.
The requirement to have the patch package have the same name as the original install complicates user downloads of the packages a bit, though I ought to be able to cause a rename of the downloaded item.
Please note that your patch can have any name. The target and upgraded packages must have the same names.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
bkandler
Posts: 4
Joined: Fri Dec 24, 2010 10:45 pm
Location: Arroyo Grande, California
Contact: Website

Re: Installing New Application Version

Here is where I found the note about command-line options in your help file.
If you are building an EXE package with the files inside, you need to extract its contents in order to create a patch. In order to do so, you will use the "/extract" command-line option of the bootstrapper, as specified here.
Regarding names. Nomenclature and undeclared antecedents will get you every time. The package has a name which is distinct from its file name. Your help file talks about package and product names and I was talking about file names.

Bill Kandler

Return to “Common Problems”