Page 1 of 1

Hardcoded Paths to checkmsi20.mia and setupmsi20.mia???

Posted: Tue Mar 23, 2010 8:31 am
by stebi
Hi,

just set up a new build server running Windows 7 64 Bit. My build runs on a Windows XP machine before. On Windows XP, Install Aware (Version 9) was installed in "c:\Programme\InstallAware". On Windows 7 its located in "c:\Program Files (x86)\InstallAware". Running the build from command line via "miabuild.exe" it stops on the new machine complaining that it cannot find "c:\Programme\InstallAware\runtimes\setupmsi20.mia". WTF? I looked into the .mpr-project file and there is the path hardcoded, but it's not editable in InstallAware Studio. Saving the .mpr file it replaces the path magically with the correct one. But guess what happens if I check in the project file and try to build on the window xp machine. Bang! Path not found on this machine. What can I do to make it build wherever Install Aware is installed in?

Re: Hardcoded Paths to checkmsi20.mia and setupmsi20.mia???

Posted: Thu Apr 08, 2010 12:12 am
by Frank
I copied the scripts to my project folder. Removed the script from the project and added them again but this time using the version in my project folder. It seems to work. Maybe that'll do it for you too.

I did notice that icons (.ico) can be put in another folder. Our products uses the same icon for every product, but when I create a shortcut and point to the .ico file in another folder than the project folder, the .ico is simply copied to the project folder and that version is used. Why?

Also I didn't figure out how to use relative paths in the Install Files commands. Ofcourse I can edit the script and it'll work fine on my machine, but now I move to another machine and checkout the source from source control and on to a different drivenumber, all of a suddens IA seems to 'remember' that it need drive Q. Where is this information stored?

InstallAware guys?

Re: Hardcoded Paths to checkmsi20.mia and setupmsi20.mia???

Posted: Thu Apr 08, 2010 12:53 am
by stebi
My initial problem seem to be solved now. It seems that I have to open the GUI Application once before I can build via command line. Maybe there are some registry values set by the application which are needed by the command line version. But the error message is missleading. There should be a clear statement what to do or it should just work.