Trying out the trial I have a problem.
How do I put files into my intended target directory?
Yes, sounds idiotic, but in the files visual editor I have $PROGRAMFILES$ as target. Now, my target folder is (Project properties) $PROGRAMFILES$\\$TITLE$
I CAN add a title with the Folder's name into $PROGRAMFILES$, but then I miss the automated renaming when the user retargets. Or would a folder named $TITLE$ automatically be renamed?
And here more problems start. I can not add a FOLDER for purely orgainzational purposes in the Visual Files editor. On the lower half, where the install is shown:
* On the left, I only have (for $PROGRAMFILES$) two deactivated entries in the context menu: Edit and Delete.
* On the right I can add a folder, but this brings up a dialog and adds the dialog.
This means that I need to have the same layout in the install than on the disc. VERY unconvenient.
Please advice.
And another topic:
I Realized when I include a folder that I can work with wildcards (*.*). What about EXCLUSIONS? Like "include everything except the .bak files".
Target Directory?
The intended target directory (as chosen by the user) is $TARGETDIR$ - just use this variable. It is similar to the %MAINDIR% used in Wise, I believe.
You cannot directly edit folders in the Files visual view, but once you have added a file (or a group of files), you can set them to go into any folder. To do this select the files in the right bottom view (or to modify an entire folder, select the folder in the left bottom view). Right click and choose edit, this reveals the Install Files command that is actually installing the files in the script for you. In the Target Folder field, type anything you like. I have shown some example values below:
And so on
Once you have a file installing into such a folder...the folder appears itself in the hierarchy and you can directly add files into it. Sorry for the inconvenience there!
You cannot directly edit folders in the Files visual view, but once you have added a file (or a group of files), you can set them to go into any folder. To do this select the files in the right bottom view (or to modify an entire folder, select the folder in the left bottom view). Right click and choose edit, this reveals the Install Files command that is actually installing the files in the script for you. In the Target Folder field, type anything you like. I have shown some example values below:
Code: Select all
$TARGETDIR$
$TARGETDIR$\\a sub folder
$WINSYSDIR$
$WINDIR$
And so on

What is confusing is that there is an inconsistency. If you create a project using the Project Wizard, there is a %TARGETDIR% node by default in the "Target Folders" tree view in the "Files" Panel. This is what is expected.
However, if you create a new project from a project template, i.e., Win32 Script, the %TARGETDIR% node is missing. It appears that in order for the %TARGETDIR% node to appear, the "Target Folders" node must be selected before you add a file. IMHO, this it would be more intuitive if the %TARGETDIR% node was included by default at least for this project type?
Thanks
However, if you create a new project from a project template, i.e., Win32 Script, the %TARGETDIR% node is missing. It appears that in order for the %TARGETDIR% node to appear, the "Target Folders" node must be selected before you add a file. IMHO, this it would be more intuitive if the %TARGETDIR% node was included by default at least for this project type?
Thanks
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Hi GoDanno
Let me try to explain why that inconsistency exists. The visual views in InstallAware automatically parse your setup script and render that information for you visually (and let you update it visually).
With templates, no files have been chosen to be installed yet, so $TARGETDIR$ does not appear in the target folders list yet.
With the Project Wizard, you will most likely have chosen at least a file, and therefore $TARGETDIR$ does appear in the target folders list.
Note that if $TARGETDIR$ doesn't appear yet...just select the top level item "Target Folders" and then add your files or folders...$TARGETDIR$ will be created for you and everything added underneath it, to help work around this potentially confusing situation.
I hope that helps clarify the mystery! Also note that as you add more directories to your setup script, for instance using Get Folder Location commands, they will start appearing in the visual view also. Nothing is hard-coded in InstallAware - that's the beauty of it!
Thanks!
Let me try to explain why that inconsistency exists. The visual views in InstallAware automatically parse your setup script and render that information for you visually (and let you update it visually).
With templates, no files have been chosen to be installed yet, so $TARGETDIR$ does not appear in the target folders list yet.
With the Project Wizard, you will most likely have chosen at least a file, and therefore $TARGETDIR$ does appear in the target folders list.
Note that if $TARGETDIR$ doesn't appear yet...just select the top level item "Target Folders" and then add your files or folders...$TARGETDIR$ will be created for you and everything added underneath it, to help work around this potentially confusing situation.
I hope that helps clarify the mystery! Also note that as you add more directories to your setup script, for instance using Get Folder Location commands, they will start appearing in the visual view also. Nothing is hard-coded in InstallAware - that's the beauty of it!
Thanks!
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
Who is online
Users browsing this forum: No registered users and 114 guests