Generating multiple builds from a single project

[stampy]

Hello,

I’ve been working on automating the builds of my InstallAware setups (trying to make my life easier ). I’ve got about 12-14 IA builds that I want to generate from a “common” IA project. In my design, the majority of the behavior is common for these 12-14 builds where the difference is just pretty much limited to the files that get installed, a bit of script logic differences, the Title of the resulting setup, and the Product Code. I strategically placed “Compiler Variables If" blocks surrounding the unique sections of script and I provide the values of the compiler variables when I build in the command line. Note that I also use a Compiler Variable for the “Product Code”, the Custom Folder, and the Output File Name which also gets passed in on the command line.

So far, so good. I can build each of the setups just fine. I can install/maintenance/uninstall each of the setups individually and each work just fine. But, when I install one setup and then install another setup, the second setup fails with an error: “A network error occurred while attempting to read from the file: <some long path in TEMPDIR\\mia_something\\<a_file_from_my_first_setup.msi>”. If I then uninstall the first, then I will able to successfully install the second.

So my questions are:
- Is there something in addition to the Product Code I need to pay attention to? When individually installing each of my setups, I see the correct Product Code GUID getting set in the HKLM\\...\\uninstall area.
- Is this an improper design? Is there a better way to accomplish my goals? I recall earlier advice about being careful with using Compiler Vars in project properties, but so far it seems like I’ve steered clear of any potential problems. I’d prefer not to have to create and maintain 14 separate setups (with a few more coming along soon) even though they are so similar.
- Is this error perhaps a side-affect of the IA/IDE?

Thanks in advance!

[CandiceJones]

Hi Stampy!

Your design sounds great to me!
Please double check that each package has unique product AND unique revision codes. This might be the problem.

[stampy]

Ah, the ol' the revision code . I added /r to the command line and it works fine now. Thanks for the help!