InstallAware

MIABUILD.EXE will not produce an error if you open a project which has a reference to script file which does not exist on the machine. If you use the InstallAware UI and try and build it immediately fails and tells you which file is missing. I am using version 5.31

I have seen references to other threads telling the user to open the (.MPR) file by hand and remove the hard coded path references to the scripts. This is precarious at best considering how the files are laid out especially if you made a mistake and saved it unknowingly. I would also argue that the UI should allow the user to specify that a script file is either relative to the project or uses an absolute path.

In a multi-dev environment where you have more than one person working on a project it is likely that their project folder is different from another developers or even more likely it could be on a different drive. And more likely that they have a different environment from a build machine.

MIABUILD.exe should produce the same error and halt the process rather than continuing on and producing an installer.

Yes - R&D is currently working on adding relative path support to include scripts and your main project script file, so this should be available soon.

We ran into this problem as well. What I ended up doing is using subst to setup some virtual drives. Each developer can map the virtual drives to whereever they like.

But, be sure to always start/open the project from the non-subst drive, and be careful to only add files to the project from the subst drive.