InstallAware

Given "My App 2.1", what's a good practice to create an installer for v2.2, so that 2.2 is recognised as being in the same 'family' as v 2.1?

My thoughts are to use Save Project As... to create a new installer from 2.1 for 2.2. That way the Product Code remains the same. My understanding is that it's this that links versions of the same product together. Is that correct?

What would be the effect of generating a new Product Code for v2.2, on the installation using the installer created this way, compared to one created with the same Product Code?

Regards, John

Dear John,

Given "My App 2.1", what's a good practice to create an installer for v2.2, so that 2.2 is recognised as being in the same 'family' as v 2.1?

Keep the same project PRODUCTCODE and UPGRADECODE.

My thoughts are to use Save Project As... to create a new installer from 2.1 for 2.2. That way the Product Code remains the same. My understanding is that it's this that links versions of the same product together. Is that correct?

You can make a copy of your entire project folder or use Project Save As as well. Personally I always use the second option.
Just a note, after you saved your project to a new folder, open it within the IA IDE and then update your project to use the correct MAIN script file under the new project folder. To proceed with, switch to MSI code view in IA IDE and from the left tree pane, select the main script file under the Script node. Right click and choose "Save script File As" to store it under your new location.

What would be the effect of generating a new Product Code for v2.2, on the installation using the installer created this way, compared to one created with the same Product Code?

Your 2.2 version will not remove your previous version ... because it is treated as different application.

Regards

Thanks very much, Francesco.
I had used Save As..., and I was going to ask why I didn't have an mia file. Now, I don't need to!

John