InstallAware

I've been testing InstallAware Studio for a while now.
The scripts I created were approved by my project-manager and I have the approval of purchasing InstallAware.

That brings me up to the next problem.

The time I've been testing InstallAware I've stored the projects on the local disk of my laptop.
The setup containes up to 54 files to be installed, and are stored inside the project like this :



Because these projects will be used by our developers, it is necessary to move the projects (and all of it's files) to our company's network environment.

A couple of questions:

1)
Will the mpr-file load correctly if moved?

2)
How can I quickly change the pathnames [C:\\IAProjects\\...]
without having to change all of the 54 files manually.

3)
Can we use servernames or must we use Drive-letters?


4)
Can we use (compiler) variables to store the sourcepaths ?
like this:



5)
How can I use the projects (and i'ts files) off-line on my laptop, after copying the files (back) to the laptop?

Ton_B wrote:1)
Will the mpr-file load correctly if moved?

There should be no problem. Please check the .mpr-file if there is any absolut path - if so, remove the path

Ton_B wrote:How can I quickly change the pathnames [C:\\IAProjects\\...]
without having to change all of the 54 files manually.

Simply use the replace function in the edit menu

Ton_B wrote:4)
Can we use (compiler) variables to store the sourcepaths ?
like this:

Code: Select all

 Set Variable $SOURCEPATH$ to "\\\\Servername\\Projects\\Project_1\\Setupscript\"

Install Files $SOURCEPATH$\\File1.dll to $WINSYSDIR$
Install Files $SOURCEPATH$\\File2.dll to $WINSYSDIR$
Install Files $SOURCEPATH$\\File3.dll to $WINSYSDIR$
...

This is not possible.

Ton_B wrote:5)
How can I use the projects (and i'ts files) off-line on my laptop, after copying the files (back) to the laptop?

I recommend to use a new drive letter (Z:, X:, ...) as source of installation files. The drive letter can be created as a network drive or via the subst command - so you can use the same drive letter with the copied installation files off-line with your notebook.

<i>Ton_B wrote:

4)
Can we use (compiler) variables to store the sourcepaths ?
like this:
Code:
Set Variable $SOURCEPATH$ to "\\\\Servername\\Projects\\Project_1\\Setupscript\"

Install Files $SOURCEPATH$\\File1.dll to $WINSYSDIR$
Install Files $SOURCEPATH$\\File2.dll to $WINSYSDIR$
Install Files $SOURCEPATH$\\File3.dll to $WINSYSDIR$
...


This is not possible.
</i>

We are currently using compiler variables for the source files, although the paths used are specified using Drive letters
e.g
Install Files #RXDSOURCE#\\Building\\readme.txt to $TARGETDIR$I have not tried with Script variables, only Compiler variables.

I guess the answer is
<B>Yes</B> you can use compiler variables to specify source files
<b>No</b> you cannot use UNC paths
Well thats my experience so far

YOU CAN use compiler variable like the example you said to store paths, but you cannot store UNC paths.

Also it would be better if you categorize your files into Directories and use Wildcards to install them
eg
Set Variable MYPATH to "C:\"
Set Variable $MYPATH$ to MYPATH

C:\\IAPROJECTS\\toWinSYSDIR\C:\\IAPROJECTS\\toWinDirand then use

Install Files to $MYPATH$\\*.* to $WINSYSDIR$

Gizm0 wrote:YOU CAN use compiler variable like the example you said to store paths, but you cannot store UNC paths.

Also it would be better if you categorize your files into Directories and use Wildcards to install them
eg
Set Variable MYPATH to "C:"
Set Variable $MYPATH$ to MYPATH

C:\\IAPROJECTS\\toWinSYSDIR\C:\\IAPROJECTS\\toWinDirand then use

Install Files to $MYPATH$\\*.* to $WINSYSDIR$

I checked this out and the described procedure hasn't worked for me: Error during build: No files matching pattern "$ZPATH$\\md128C2.ttf"

I also tested compiler vars (#ZPATH#) and this also didn't work.

cu

Markus

casic wrote:

Gizm0 wrote:YOU CAN use compiler variable like the example you said to store paths, but you cannot store UNC paths.

Also it would be better if you categorize your files into Directories and use Wildcards to install them
eg
Set Variable MYPATH to "C:"
Set Variable $MYPATH$ to MYPATH

C:\\IAPROJECTS\\toWinSYSDIR\C:\\IAPROJECTS\\toWinDirand then use

Install Files to $MYPATH$\\*.* to $WINSYSDIR$

I checked this out and the described procedure hasn't worked for me: Error during build: No files matching pattern "$ZPATH$\\md128C2.ttf"

I also tested compiler vars (#ZPATH#) and this also didn't work.

cu

Markus

Strange, i have almost the same thing working on me.. Let me take a deeper look and create an working example..