You can also define Windows Mobile files, shortcuts and registry's entries that are language-dependent. To do that, first you will need to define a Windows Mobile Component for each language you want to support, setting the Language property of each Windows Mobile component to the correspondent Setup Language, like the following example:

 

 

After defining the Windows Mobile components, you will need to select all files you want to distribute with each Windows Mobile component. Note that for Windows Mobile files, shortcuts and registry's entries the procedure of defining the multi-language items is a little bit different; for setup files, shortcuts and system configurations you just change the Language property for the language-dependent items, but for Windows Mobile files, shortcuts and registry's entries you must to select the Windows Mobile component that represents the language you want for all items you want to distribute, including the language-independent items, because each Windows Mobile component corresponds to a different Windows Mobile setup package, and the items that you do not set the Win CE Component property, VisualSetup interprets that these items are items of the Default Component, that exists in all setup projects. For more information about Windows Mobile components, please read the Windows Mobile Components topic.