Hello,
We have 8 advanced installer enterprise projects that work fine for our 8 products. During the year 2008 we released newer installations for the same products that were named with service pack 0,1,2,3, according to the specific SP. These new installations were designed to replace the current product installation in the user machine with the new installation. All what we needed to do to accomplish that was to copy the current AIP file, choosing to automaticly upgrade older product versions, changing few parameters, like the product name, version and registry values, and that's it.
Till here everything is fine, The problem started when we needed to release the same products for the 2009 release with SP0. At this case we were not supposed to replace the current installation in the user machine (which is 2008 release with SP0,SP1,SP2,SP3), because he\she can work with both versions of our product side by side. In Other words, we should treat it as a new product installation.
We know that we can open a new AIP file and start building the whole project from scratch, but we cann't allow ourselves such wasted time.... we need the same project to be copied with little changes from our 2008 project, and let it be a new project for 2009 with SP0, that has no connection with any previous instances of 2008 (In other words we need it to be able to be installed side by side with the previous year products).
We cann't just go and choose the allow side by side installs of different product versions, because there could be other service packs that we might release during the year 2009 that will need to upgrade the 2009 SP0 installation but not the 2008.
I hope that my question is clear...
Please your answer urgently,
Thanks in advance,
Abed
FOLLOW US
Get the latest news in Application Packaging