Hi Nicolas,
I have checked the right procedure to change the system local, and it is set to French (it was already set to French). I built a MSI with bootstrapper option (this is equivalent to build a MSI with no bootstrapper): launching the MSI directly should use the system locale, but it is not. The installation is in English.
Please note that using a bootstrapper with the default options for a multilingual package will use the system language, not the system locale.
Basically, when using the bootstrapper there are two options:
1) "Automatically use system language for installation" - the
system language is used. If the system language is not included in the package, English is used.
2) "Display language selection dialog (for multi-language packages)" - the user chooses the installation language. For a completely silent installation the
system locale is used. If the system locale is not supported by the multilingual package, English is used.
When not using a bootstrapper the following happens:
- the
system locale is used; if the system locale is not supported by the multilingual package, English is used
An important note is that the "Display language selection dialog (for multi-language packages)" option uses Windows Installer transforms to tell the package what language to use. Therefore, if you use this option but you launch the MSI directly, no transform is used so English is always the installation language.
Basically, when using an EXE bootstrapper for your package some specific elements and changes are used in order to provide the bootstrapper functionalities. Therefore, launching the MSI directly when you built it with a bootstrapper may not have the same result as launching the EXE.
Please note that a different MD5 signature is generated every time you build the package. Therefore, modifying the project and building it will generate a new MD5 even if nothing was really changed in the MSI.
Regards,
Cosmin
FOLLOW US
Get the latest news in Application Packaging