1 reply to this topic

[chris tyghe]

Hello,

I have created a SILENT install, which has the logic to 'potentially' spawn 3 satellite setups. I then used this setup to create a PFTW.

Other divisions of my company would like to leverage my installer. However, not all divisions require ALL 3 satellite setups. Each division/product will have unique 'satellite' needs, i.e. 1 of 3, 2 of 3 etc.

My plan was to create 3 separate *.iss files and instruct these divisions to pass a parameter, i.e.

setup.exe -f1a:\other\alternat.iss


Given that this is the first time this request has come to me, I was wondering if there are potential pitfalls I might not be aware
of or perhaps this is NOT the best way to do it.

Any suggestions would be appreciated.

Thank-you.

[Taco Bell]

That would certainly be one way to do it.  I'll think about it some and see if I can give you a better idea.