Page 1 of 1

Uncompressed directory layout, folder structure

Posted: Mon Jan 26, 2009 4:52 am
by garyk
I have a project using the Uncompressed directory layout.
When IA builds the project it places all the files I specify with the "Install Files" command under a folder structure that looks like:

Project->Data->DefaultFeature->1ABEA348->AF57E17D->my file1
Project->Data->DefaultFeature->5ABD56E1->BF34F17C->my file2
Project->Data->DefaultFeature->3224F346E->DE27E17A->my file3
etc...

I am using Uncompressed directory layout so that I can have maximum control over the installer structure, but with this layout I can't do anything with my installed files.
Can IA be made to use a single flat folder or a folder structure that represents the source files structure on disk?

Thanks
Gary

Posted: Mon Jan 26, 2009 7:05 am
by MichaelNesmith
InstallAware needs to have full control over all these paths at all times, to facilitate things like one-click patch creation from your projects. You cannot make any assumptions about this folder structure as it might also change in future versions.

If you need to have files lying out flat in your source media, you can have them wherever you like and then copy them using Copy Local Files or other similar functions.

Posted: Mon Jan 26, 2009 8:33 am
by garyk
Thanks for the reply Michael.

I don't want to reduce IA's control over these paths. I want the ability to replace files with newer copies (same name, same path) without rebuilding the installer.
If these paths where more inteligable I could easily do it, but the encryptic names make it too hard.
Also I have notices that assemblies ARE saved with thier original source path. Why the difference and why isn't that possible for other file types?

Thanks
Gary

Posted: Mon Jan 26, 2009 5:15 pm
by MichaelNesmith
You should NEVER manually drop-in files. InstallAware generates MSI table information any time you do a build, and this information may be out of date if you just drop-in replacements without doing a full build (and thus, a refresh of the MSI database). This can lead to completely unpredictable and/or misleading errors in your installation.

I am sorry there is no easy solution for you.