Suggested Actions

Suggest an improvement

Submit a request for new functionality or enhancement to an existing feature that would make the product behave more efficiently or extend its capability.

For Example:

  • I would like to see products differently.

  • I would like to see the product do something new.

  • I have an idea for how the product could be improved.

Open a support case

Create a new support case to get help with a problem you may be experiencing. This if the product behaves in a way in contravention to the documentation or displays an error visibly or in any log files or debug.

For Example:

  • I cannot get the product to work the way i want.

  • I donot understand something about the product.

  • I believe I have discovered a problem with the product.

This website uses cookies. By clicking OK, you consent to the use of cookies. Click Here to learn more about how we use cookies.
OK
wimcolgate
Pilgrim
‎Jun 05, 2013 07:47 PM

Single .ISM, multiple release targets; different INSTALLDIR targets, what's best way?

Hi have a single single .ISM Basic MSI project.

Under releases I have 2 different targets: 64bit, and 64bit-BETA. Each release needs to target a differently named installation directory.

For example:

c:\program files\MYPRODUCT
and
c:\program files\MYPRODUCT-BETA

What's the easiest way to accomplish this?

I probably have glossed over the right way to do it and got mired in the wrong way ... but what I had done was to add different release flags to each of the releases: then during the install, if BETA -- add "-BETA" to the installation directory. But I'm sure you will spot the problem right away.

Changing INSTALLDIR after CostFinalize doesn't update all properties derived from INSTALLDIR (not quite sure how the UI Dialog figures out how to do it when manually changing the install directory!).

Before CostFinalize, I don't know what the base (or original) installation directory is. If I could extract before CostFinalize, I'm OK with that.

Thanks,

Wim
Labels (1)
0 Kudos
Reply
4 Replies
regexmaster
Occasional contributor
‎Aug 07, 2013 10:27 AM

Same question

I have exactly the same same situation and question, and am still looking for the solution. Any guidance would be very much appreciated.
Many thanks
0 Kudos
Reply
regexmaster
Occasional contributor
‎Aug 07, 2013 11:00 AM

Found a helpful thread

I found this thread, which looks promising...
Setting INSTALLDIR in Custom Action doesn't change install location
0 Kudos
Reply
AmitRout
Pilgrim
‎Aug 08, 2013 08:29 AM

Re: Single .ISM, multiple release targets; different INSTALLDIR targets, what's best way?

Have a look

http://blogs.flexerasoftware.com/installtalk/2011/01/building-32-bit-and-64-bit-installations-from-t...
0 Kudos
Reply
regexmaster
Occasional contributor
‎Aug 08, 2013 11:23 AM

Re: Single .ISM, multiple release targets; different INSTALLDIR targets, what's best way?

Very nice - Thanks!

AmitRout wrote:
Have a look

http://blogs.flexerasoftware.com/installtalk/2011/01/building-32-bit-and-64-bit-installations-from-t...
0 Kudos
Reply