First of all, I am pretty new to the Windows Installer system (and AI). So it is possible that I may use the wrong term, or I didn't gasp the idead behind the the details...
We are currently working on a project with the following requirements:
1) Multi Language Setup: the user must be able to select the installation language
2) A main program and some tools
3) Many "media" files, some databases... just a bunch of data files
4) Patches for all the above
The main program and the tools are language "neutral" (we have our own logic in the program files and database for all the supported languages).
Actually we only need to have the setup in different languages. There is no need to have different "packages" for the program or data files.
The question is, how should we organize the AI (Enterprise) project? The basic setup using multi-language MSI works, but patch creation fails (I have read the posting "thanks, now problem with patch for a multilanguage setup"). There should be an easy way to generate the patch files (msp or exe?).
The media files are somewhat large (even for a DVD as target). (Currently) We have 14 languages, so it wouldn't be a good idea to have 14 copies of the same files. Is it possible to put those "data files" in its own package? Is it still possible to generate patch files.
Sometimes we need to update the data files only, and sometimes we need to update the program files (and their DLLs) only. Maybe we need to update both of them.
How can all of this accomplished, please?
FOLLOW US
Get the latest news in Application Packaging