Advice on Install and updates Architecture for composite? - 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!

adex303
Posts: 1
Joined: Thu Apr 24, 2008 8:34 am

Advice on Install and updates Architecture for composite?

Hello, I'm currently testing advanced installer and its update feature, I'm not sure that it can offer me what I'm looking for...
I need it for a specific project but I'm a bit confused about the best hierarchy to adopt in term of installation and upgrade.
Best regarding efficiency, stability, and easiness to maintain.

The core application playbacks elements which are located in a subfolder "content".
Content folder contain "packages" gathered each time in a folder (a folder with files and subfolders). At initial install only one "package" is installed (named A).

EX: Initial install:
Core application
-------------------|_content
------------------------------- |__A

The user cannot choose which package to install at first install or during subsequent upgrades. It is intentional that when an upgrade is done everything is installed.
Most of heavy files are located in "packages" located in content folder.

When an update is done, it may:
update core application files (all or some+add/remove some or leave it as it is)
update a package already installed (all or some+add/remove some or leave it as it is)
add a new package

Exemple of first update:
Core application (some files modified)
-------------------|_content
------------------------------- |__A (some files added and some removed)
------------------------------- |__B (new package added)
------------------------------- |__C (new package added)


The content folder may contain more than 10 packages. So I'd like to avoid the approach of repackaging everything each time which may result in a huge installer file, bigger at each update.
Are patches relevant to such a situation?
Does features give me an advantage for the update phase even if the user won't be allowed to select them? (I mean gathering each "package", A,B,C,.. respectively in a sub feature).

What about merge modules, is it something relevant in my situation and may it smooth my project organisation?

Should I consider an installer per element? 1 installer for Core application, and then 1 for each "subpackage"? (I'd like to avoid this approach in order to simplify the update phase.)

Thank you very much in advance for your suggestions.


adex
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Advice on Install and updates Architecture for composite?

Hi,

Thank you for your interest in Advanced Installer.
Are patches relevant to such a situation?
If the upgrade is basically adding or updating some files and folders and you don't want to perform complex operations, then a patch is recommended. A Windows Installer patch is basically the difference between two MSI packages, therefore you would distribute the actual update, not the entire installation package.

You can create a patch by using a patch project and by following the patch tutorial
Does features give me an advantage for the update phase even if the user won't be allowed to select them?
For your case there are no real advantages offered by organizing the package into features (except allowing you to manage the project better because the components wouldn't be all under that same feature).
What about merge modules, is it something relevant in my situation and may it smooth my project organisation?
Merge modules are normally used when you want to include a part of an installation package into multiple projects. If you want to use them in a single project then their use is redundant.
Should I consider an installer per element?
If the update process is simple (just add and update some files and folders), then a patch is the best solution. I'm not sure if a per-element installer is a good solution because it would be hard to maintain them (create each new version of each package and deploy it).

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”