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
FOLLOW US
Get the latest news in Application Packaging