IA project files

Got a problem you cannot solve? Try here.
Post Reply
jweksej
Posts: 93
Joined: Wed Sep 27, 2006 4:54 am

IA project files

Post by jweksej »

IA project contains bundle of files located at <ProjectName> folder tree.
1. Which of them are key files and should be stored in repository (like cvs) to fully restore the project?
2. Is this list of files constant or it changes with project complication?

Is it possible to have all project data in one text file?
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

I think this is documented in the help files - please take a look there.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
jweksej
Posts: 93
Joined: Wed Sep 27, 2006 4:54 am

Post by jweksej »

Unfortunately no :( . At least I don't found what I was looking for.
First of all is <project>.mpr file . In contains a list of *.dfm (binary), *.dfm.miaf (text) files (looks to be dialogs data) and update.ini (text) file. Other files in folder are <project>.mia <project>.mia.brk <project>.mia.fld

Structure of project files is not described anywhere.
Which of them are crucial and should be stored in repository?
Which are not important and can be generated by IA on the fly?
The list of files can change during project development and can be a source of errors if something will be missed.
For me crucial will be feature allowing to (re)store all project data to one text file - kind of text (xml?) archiver - and this file will be stored in repository.

Irt was annoying me in InstallShield - continue add/remove files to/from repository.

Can you give me workaround for this?
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

.MPR: Project file, contains project level settings and references to scripts, dialogs, support files, merge modules, etc.
.MIA: Script file, either your main setup script, or your include scripts
.MIA.BRK: Breakpoints for the named script file
.MIA.FLD: Code folding for the named script file
.DFM: Dialog design
.DFM.MIAF: Dialog rules
.DFM.BAGGAGE: AVI or other "baggage" files to be kept next to the .DFM file on each save

Let me know if I missed anything!
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
binkle

Post by binkle »

I think you missed the *.tanslations.* files for translations.
I suppose they are necessary too.

Greetings

Harry
jweksej
Posts: 93
Joined: Wed Sep 27, 2006 4:54 am

Post by jweksej »

Thanks, but what with remaining questions?
Tiago
Posts: 129
Joined: Thu Jun 18, 2009 9:08 am

Post by Tiago »

As far as I have seen, the list provided by mr. Nesmith includes all the file extensions. I usually remove files with the BAK, DLL and TXT extensions, plus to the "Release" subfolder, before storing my projects in our repository. That's all I have needed so far. And by the way, only DPR files are binary.
[b]Tiago Rocha[/b]
[i]Product Technology[/i]
www.ppi-multitask.com.br
Post Reply