InstallAware

Hi there,

Since source control systems typically let a user set a root for their local code depots, we find that our developers place their code in all manner of places on their machines.

We are currently considering rewriting our software installer in InstallAware, but a sticking point is the fact that the "Install Files" command requires a full, variable-free path to the source files. InstallShield allows path variables (several built-in) that allow the use of relative paths - locations that are found with the install project as the focal point. But IA requires a full, non-relative path, meaning that, for all our developers to build the installer, they would need to create a local code depot that exactly matches whatever the "Install Files" command points to, to be able to build on their machines.

Are project path variables (and the ability to use them for "Install Files") a consideration for future versions of IA? Or was it a conscious design decision to require hard-coded paths?

Install Files is working well for me using a variable and relative path. For instance:

Install Files #PROJDIR#\\..\\HelpFiles\\UserManual.pdf

and

Install Files #BUILDDIR#\\bin\\MyAssembly.dll

where $BUILDDIR$ is a compiler variable that is defined as:

#PROJDIR#\\..\\build\\#BUILDCONFIG#

and $BUILDCONFIG$ is a compiler variable that defaults ot "Release."

While I have had success with variables and relative paths for "Install Files," I have had no such luck with setting the Ouput Path in Project Options. You cannot use variables or relative paths there. It's a pretty jive limitation, IMO.