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!

kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Major Upgrade question (that is not MSP-based)

Hi,
Our full setup file can be up to 85MB in size, but much of this is runtimes (vb6, .NET 2, VCRT 2008, VCRT 2010, etc.); with MSI installations I would like to know what I can do to make our installer packages smaller.

With our old installer we had a Full Setup that was our program EXEs, DLLs, and supporting Data files, plus all required runtimes. Our customers have to install this as their initial install, to ensure they have the required runtimes as well as answer some configuration/settings prompts about. Then, after bug fixes are ready we provide an Update install file that has our Program EXEs, DLLs and supporting data files, but it has NO runtimes. This often shrinks our Update installer package down to about 20MB, so a substantial savings in download time / disk cost / installation speed etc.

How does one go about this with MSI technology (without using MSP; which we cannot use as our app violates one of the many rules that enable MSP to work)?

Alos, how would do I make that Update installer package (again, not MSP-based), so that if our app is already installed and the user wants to install our the update they only get minimal dialogs (not the full setup dialogs). Our full setup collects all the other details, such as where the app should be installed, the user's name, etc., etc.

Thanks in advance.
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Major Upgrade question (that is not MSP-based)

Hello,

A major upgrade is essentially the removal of an older product which is replaced by a newer product. In Advanced Installer the upgrades can be configured from the Upgrades View.
Basically, the upgrade process performs the following actions:
  • Detect and completely remove older products.
    Install the new product.
In order to display only a dialog with a progress bar showing the evolution of the installation and the message boxes that display error messages you can enable the Limit to basic user interface (simple progress and error handling) option from the Install Parameters page.

Also, you can even decrease the installation package size by using the LZMA Compression from the Media page.

Please let us know if that helped, otherwise give us more details about your specific scenario.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Re: Major Upgrade question (that is not MSP-based)

Hi Daniel,
Is there an example/tutorial of how just before the Removal of the old product we can open an INI file and use some of it's values to pre-populate the dialogs when installing the new product? Or better yet can the INI file be left behind during Uninstall so that it's user settings are not lost?

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

Re: Major Upgrade question (that is not MSP-based)

Hello,

If you're looking to preserve the old database files during upgrade, here's the How do I prevent a file or registry entry from being uninstalled or repaired? article which may be useful.

Please let us know if that helped otherwise give us more details.

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

Return to “Building Installers”