Need Advice with Project Structure Idea - Advanced Installer Community
AndreG
Posts: 57
Joined: Tue Jun 10, 2014 11:41 am

Need Advice with Project Structure Idea

Lately I've found myself building many installer packages that are actually made up of multiple applications. So far, I've found creating installers as MSI packages and importing this into another installer as a dependency has turned out to be the cleanest way to do this.. Update a dependency, and it's update installer is launched if required on the target machine. However, this doesn't really give me much control over each individual applications' current installation states..

While looking a few different AI options, I thought perhaps Modules was the way to go for this structure. But, as pointed out in this thread, these apparently don't support one very particular feature my environment requires. In my case, the files in question are run-time files that are unfortunately not created by the application that relies on them, but they are used for long-term storage (SQLite3 DB files), so they must never be overwritten if they exist.

Thinking a bit more "out the box" here, the most versatile approach would be to have an "installation laucher" of sorts. Effectively an installer that has multiple imported installers that can be launched individually from an installer page with custom buttons.. Each of the bundled packages could store machine-specific installation info on the target machine, which the core installer could be designed to check for and react to accordingly (hide/show different options, update current configuration, etc.). However, this also seems like a lot of work in the setup stages, which makes me wonder if it's not perhaps going to create unnecessary work maintaining them down the line.. Nothing a few batch build files can't resolve, but again, more to maintain down the line.

Has anyone got any experience with multi-product installation packages like this..? I've pretty much been thrown in the deep end with installation package feature requests, so I'd really appreciate some suggestions / ideas for getting around this. :)
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Need Advice with Project Structure Idea

Hello,

If you don't want to create a separate installer for every product installation you have and afterwards bundle them into another wrapping installer, then you can try to add all of your packages installation resources (files, folders, registries, etc.) into one project. Next, in "Organization" page, you can create and design separate features for all of your package installation resources.

Also, you can create your own custom feature selection dialog or you can use the predefined "SetupTypeDlg" dialog.

If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
AndreG
Posts: 57
Joined: Tue Jun 10, 2014 11:41 am

Re: Need Advice with Project Structure Idea

Hi Daniel,

Thanks for the suggestion, I had previously considered using features to separate the different areas of the software suite, but at that time I didn't see how viable that route would be. Must admit, I've learnt a lot about AI since then, so maybe I should give that another go. The only thing that concerns me is having multiple applications suites that depend on a common folder/file structure, this has the potential to get messy very fast with more complex installer packages..

On the other hand, I might very well be going in the wrong direction from the start here.. I'll dig into the conditional features idea with a fresh start and see what happens, maybe the whole structure needs a re-think anyway. :) I'm not going away for the holidays, so I'll be taking work home to help pass the time while I'm "on leave".
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Need Advice with Project Structure Idea

You're welcome.

Just let us know anytime when you have a question or doubt.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”