InstallAware

I am using InstallAware 12. I have a product that is distributed by two companies. I have a folder structure like:
ProductA\Install\17.2
ProductA\Install\17.3
ProductA\Install\18.0
ProductB\Install\18.0

The scripts in ProductB\Install\18.0 were based on ProductA\Install. However, I made significant changes on the IA Files panel: new destination folders, separated out some files for special handling (instead of *.*), etc.

Today I am working in ProductA\Install\18.1. As part of the normal process, I open the prior release’s script (for example, Product\Install\18.0\Product.mpr) and use “Save As” to copy the project to the new folder (Product\Install\18.1). Much to my surprise, the changes made to Product B in v18.0 are in my Product A scripts. In fact. these changes appear in every script for the past several years - even though the change was actually made in January 2012!

How can this occur? How can I avoid this in the future? I assume there is no way to repair the scripts except from backups or manually, so I won't bother asking that.

Best,
Scott

Dear Scott,

I really think that your issue it is caused because simply, the main script in your Project for Product B still points to the file of Product A.

So when you copy a complete folder, of an already done project (as your Product A), to create a new project (as your Product A), you must check that any script used or eventually any other files must point to the new location accordingly. Note that this often happens with mainscript.mia, It is a good practice to use a common path to share eventually, other script that you have created, for common use along your projects.

for example: to do this with the main script file, simply remove the old one from Product B ( ... this still points to Product A folder), then add the correct script from Product B folder.

Of course this must be done before making any changes to the new project

Hope this helps you.

Regards

Thank you - I suspected as much but have avoided working directly with the files so far (only worked via UI).

So I see that the MPR file does in fact contain a line that points to the MIA file in the ProductA\17.2 folder.
I will move some files about and point to local versions to repair.

Best,
Scott