Hi,
maybe I am missing something obvious, but it would appear that the files that are added to creatives (supportdir) do not get grabbed dynamically when a build is started. IOW, if I have files that I have included in the creatives and they change from build 1 to build2, I need those files to be picked up from the directory dynamically. I dont want to have to go into the UI everytime I make a change to a support dir file and re-add it. Am I missing something. This makes automating a build all but impossible. I know I am missing something.
Support Files not dynamic
The files are actually copied into your installer project folder.
You can modify the support files section in your project file 'myproject.mpr'. Use a relative/absolute path and then it will pick the files up directly. The project file it self is arranged with $ separating sections just look for the file you need to alter.
But this is unsupported by installaware and does cause errors if you try and use the ide to modify these files after.
I am not sure if this would still work in version 7
You can modify the support files section in your project file 'myproject.mpr'. Use a relative/absolute path and then it will pick the files up directly. The project file it self is arranged with $ separating sections just look for the file you need to alter.
But this is unsupported by installaware and does cause errors if you try and use the ide to modify these files after.
I am not sure if this would still work in version 7
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Actually what you can use are File Bags (check the plug-in command) for a dynamic, recursing support files mechanism, resolved at build time, and web media block friendly.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
It would appear, however, that files placed in a filebag are not updated in a patch. We are working on a update that requires new functionality in one of the files in a filebag. The patch does not appear to include this updated file, however, and the old filebag contents are used.MichaelNesmith wrote:Actually what you can use are File Bags (check the plug-in command) for a dynamic, recursing support files mechanism, resolved at build time, and web media block friendly.

