Invalid MSI Filename string - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

dobrovi
Posts: 2
Joined: Fri Nov 23, 2007 12:35 pm

Invalid MSI Filename string

Hi.

I need to create installer with 2 languages - english and german (german by default).

The difference is in end user license and in one xml file, which should differ depend on selected language.

In translation/languages I have selected both languages. In localization options I have checked "User Interface" and "File System / XML Files".
I have also checked "Enable per-element localization".

In Dialogs / LicenseAgreementDlg I have selected my german eula and in localization dialog "always translate this string / using specified localization identifier:" = "Control.Text.LicenseAgreementDlg#AgreementText".


Now in "Files and Folders" I go my xml file and click on properties. In localization dialog I set there "always translate this string / using specified localization identifier:" = "File.application.xml".

Now I create ail-file:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="de">

<ENTRY id="Control.Text.LicenseAgreementDlg#AgreementText">
<STRING lang="en" value="D:\Work\myfirm\myproject\installer\windows\EULA myprojet Pro_EN.rtf"/>
<STRING lang="de" value="D:\Work\myfirm\myproject\installer\windows\EULA myproject Pro_DE.rtf"/>
</ENTRY>

<ENTRY id="File.application.xml">
<STRING lang="en" value="D:\Work\myfirm\myproject\installer\windows\application_en.xml"/>
<STRING lang="de" value="D:\Work\myfirm\myproject\installer\windows\application_de.xml"/>
</ENTRY>

</DICTIONARY>


and add it in translation/dictionaries.

Now try to build the package and in result I get this error:

DefaultBuild
Creating MSI database... done.
Creating MSI database... error.
Exception - Reason: Invalid MSI Filename string [D:\Work\myfirm\myproject\installer\windows\application_en.xml].

Build finished because an error was encountered.




Please note, that all paths are correct and these files exists on appropriate locations.

Also, if for this xml file I set "never translate this string", then installer is created and I have installer with 2 eulas on different languages...

But how can I have installer, which also can put different files into target directory, depend on the language selected?


Thank you.
Igor.
Ionut
Posts: 605
Joined: Tue Nov 22, 2005 11:29 am
Contact: Website

Hi Igor,

Please note that only for the license agreement and readme text a full path must be specified in the dictionary. For files, you need to specify the localized file names, not their full paths. This is the reason you are getting the build error.
But how can I have installer, which also can put different files into target directory, depend on the language selected?
All the language dependent files will be added in the Files and Folders page and their attached Components will have mutual exclusive conditions that will use the ProductLanguage Property. Set these conditions in the Organization page, for instance:

Code: Select all

ProductLanguage = 1033
If the language dependent files have identical names, put them in subfolders of the destination directory and for each subfolder set the option "Install folder content into the parent folder" (in the "Edit Folder" dialog).

Regards,
Ionut
Denis Toma
Advanced Installer Team
http://www.advancedinstaller.com/
dobrovi
Posts: 2
Joined: Fri Nov 23, 2007 12:35 pm

Thank you for your explanation.

Code: Select all

ProductLanguage = 1033 
Next question - where can I see possible values for ProductLanguage property?
If I could use there for example "en" or "de" etc, that would be obvious. But where can I see which number means which language?


With best regards
Igor.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”