Installing serveral products from a collection of DLLs - 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!

davidnewcomb
Posts: 19
Joined: Fri Apr 09, 2010 5:04 pm

Installing serveral products from a collection of DLLs

I'm evaluating AI and am trying to write something simple that does what I want but I have run into a couple of questions.

1) Our application is more of a framework which consists of 100 to 300 DLLs. Each application uses some number of them so it doesn't make sense (from a shipping point of view) to split them into separate packages because our customers download sizes would increase from 0.6GB to 6-7GB. There is a common set of DLLs which exist in all the products. Is it possible to create a set of DLLs to install and install them under each product (or feature) then only patch them if I update that product (or feature).

eg
\data\product-1\common
\data\product-1\the-rest

\data\product-2\common
\data\product-2\the-rest

so when I update product-2 then \data\product-2\common is patched but \data\product-1\common is not. To put it another way there may be a dependency between product-2 and common that would break product-1 and common in the new version.

2) Can I create my own pre-requisites? Some of the installation options will require some of our custom hardware to be installed. I would like to know if there is some facility to test whether the hardware exists. We can write our own hooks but we need a way to plug it into AI. Something like test at start and removing it from the component installation list or testing later and throwing up a warning.

Regards,
David
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Installing serveral products from a collection of DLLs

Hi David and welcome to Advanced Installer Forums,

For achieving the goal described in 1), you can do the following:
Let us assume runtime.dll (v1.0) is a file that is common to both product-1 and product-2. You would add it two times in the project, from the Files and Folders page. Each time you are adding the file, a new component should be created, that will contain that file. Check this from the Organization page.

Note that even if you are adding runtime.dll two times in your project, your installer will only contain one instance of that binary, so that installer size is saved.

When product-2 will need a new version of runtime.dll (v2.0), you simply change that entry from the Files and Folders page in your project file to point to the new runtime.dll (v2.0). The other entry (v1.0) needed by product-1 will remain unchanged. Now when building, the installer will contain both v1.0 and v2.0 of the file.

Regarding 2), you are trying to incorporate custom behavior into your installer. You might want to look into using a custom action.

Since you are new to using Advanced Installer, I highly recommend you follow at least the simple and professional installation tutorials. They will be a great help to you, and you will better understand how an installer works.

Do let me know if my suggestions helped.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
davidnewcomb
Posts: 19
Joined: Fri Apr 09, 2010 5:04 pm

Re: Installing serveral products from a collection of DLLs

Thanks for such a comprehensive reply.

It will not be possible to have 2 separate versions of the runtime.dll because all the code will be generated from the building of our main product.
The runtime.dll will be updated in both versions. However I would like to be able to patch one feature and not patch another feature.
So if I patch one feature can I get it to ignore another feature that may need patching. Will the AI recognise that it is the same file and update it in both places or will it ignore one of the places because it has a separate component id.

I have started on the tutorial already.

Thanks,
David.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Installing serveral products from a collection of DLLs

Hi David,
It will not be possible to have 2 separate versions of the runtime.dll because all the code will be generated from the building of our main product.
I am not sure I understand this. Could you please describe the reason in more detail?
The runtime.dll will be updated in both versions. However I would like to be able to patch one feature and not patch another feature.
If you plan on doing a major upgrade, you will have to split the common part, place the unaltered runtimes under product-1 and updated runtimes under product-2.
In a patch, you can safely change product-2 to add the new runtimes as long as they are under a different component GUID.

Regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
davidnewcomb
Posts: 19
Joined: Fri Apr 09, 2010 5:04 pm

Re: Installing serveral products from a collection of DLLs

I think this is just going to be a problem with trying to make AI squeeze a multi-product installer into a single-product installer with features mapped as products.

Our main product is built from source each time. All the DLLs are therefore built into our DLL location ready for the AI to pick them up and build the installer.
So \data\product-1\common\runtime.dll and \data\product-2\common\runtime.dll will be pointing to the same location on disk to pick up the new DLL.
So when I want to upgrade the product, I want to be able to only upgrade a particular feature.

Return to “Common Problems”