Paths to runtime

Got a problem you cannot solve? Try here.
Post Reply
smndk
Posts: 8
Joined: Wed Dec 17, 2008 5:49 am

Paths to runtime

Post by smndk »

When I add a runtime to my set up the path to the runtime is added to my mpr file. For example if I add Microsoft Visual C++ Runtime 8.0 the following paths are added:

C:\\Program Files (x86)\\InstallAware\\InstallAware 8\\runtimes\\checkvc8.mia
C:\\Program Files (x86)\\InstallAware\\InstallAware 8\\runtimes\\setupvc8.mia

Now if I add or remove other runtimes, the path to the existing runtimes is removed in such away that the above becomes:

checkvc8.mia
setupvc8.mia

And when I the try to build the setup the runtime isn't included in the setup and what's worse: No build error is raised!

Am I the only one that is experiencing this problem?

I am currently using InstallAware 8.

Kind regards
Svend
CandiceJones
Posts: 904
Joined: Thu Dec 22, 2005 7:03 pm
Contact:

Post by CandiceJones »

Actually, that's not how it works. When you add a runtime, the runtime script files are locally copied to your project folder (where the MPR file is found) and added to the MPR project file as file names without any paths, to support relativizing paths in your project files and to make them more portable. If the script files already exist, they are not overwritten to preserve any custom code you might have. This is the correct behavior you should be seeing, anything else would be a bug so let us know.
Candice Jones
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
smndk
Posts: 8
Joined: Wed Dec 17, 2008 5:49 am

Post by smndk »

CandiceJones wrote:Actually, that's not how it works. When you add a runtime, the runtime script files are locally copied to your project folder (where the MPR file is found) and added to the MPR project file as file names without any paths, to support relativizing paths in your project files and to make them more portable. If the script files already exist, they are not overwritten to preserve any custom code you might have. This is the correct behavior you should be seeing, anything else would be a bug so let us know.
Can it be because the setup originally were created with InstallAware 6?
ulrichard
Posts: 150
Joined: Thu Dec 27, 2007 5:45 am
Location: Switzerland
Contact:

diff

Post by ulrichard »

Hi smndk,

if you do a diff between your local files and the ones in the InstallAware program folder, do you see a significant difference?
www.examdiff.com
www.scootersoftware.com

Rgds
Richard
http://www.pointline.com
http://www.paraeasy.ch
http://ulrichard.ch
smndk
Posts: 8
Joined: Wed Dec 17, 2008 5:49 am

Re: diff

Post by smndk »

ulrichard wrote:Hi smndk,

if you do a diff between your local files and the ones in the InstallAware program folder, do you see a significant difference?
www.examdiff.com
www.scootersoftware.com

Rgds
Richard
Hi Richard

Which InstallAware program folder do you refer to? "C:\\Program Files (x86)\\InstallAware\\InstallAware 8"?

Regards
Svend
Last edited by smndk on Thu Dec 18, 2008 6:22 am, edited 1 time in total.
smndk
Posts: 8
Joined: Wed Dec 17, 2008 5:49 am

Post by smndk »

CandiceJones wrote:Actually, that's not how it works. When you add a runtime, the runtime script files are locally copied to your project folder (where the MPR file is found) and added to the MPR project file as file names without any paths, to support relativizing paths in your project files and to make them more portable. If the script files already exist, they are not overwritten to preserve any custom code you might have. This is the correct behavior you should be seeing, anything else would be a bug so let us know.
It seems to work the way you descripe. Except for when I create a new setup based on the Win32 template. In such a setup the "Microsoft Windows Installer 2.0" application runtime is checked but is not copied to the project directory.

What really worries me is that the build does not fail when components for some reason are "missing" and cannot be added to the setup file.

Regards
Svend
ulrichard
Posts: 150
Joined: Thu Dec 27, 2007 5:45 am
Location: Switzerland
Contact:

Post by ulrichard »

Hi smndk,

>Which InstallAware program folder do you refer to?
How many InstallAware program folders do you have?

You mentioned a file C:\\Program Files (x86)\\InstallAware\\InstallAware 8\\runtimes\\checkvc8.mia" in your first post. Compare that to the checkvc8.mia in your project folder.

Rgds
Richard
http://www.pointline.com
http://www.paraeasy.ch
http://ulrichard.ch
smndk
Posts: 8
Joined: Wed Dec 17, 2008 5:49 am

Post by smndk »

ulrichard wrote:Hi smndk,

>Which InstallAware program folder do you refer to?
How many InstallAware program folders do you have?

You mentioned a file C:\\Program Files (x86)\\InstallAware\\InstallAware 8\\runtimes\\checkvc8.mia" in your first post. Compare that to the checkvc8.mia in your project folder.

Rgds
Richard
Oh, yes the runtime files were missing from my project directory, and the mpr file refered to paths that no longer existed. I don't know why InsallAware adds paths to the mpr file when it can't find the files, and how it is able to build a setupfile without reporting any errors when it cannot find the files it were supposed to include in the setup.

It helped copying the runtimes to my project directory and removing the paths from the mpr file.

Regards
Svend
Post Reply