Output (XAP File) |
This sheet specifies the output options for a XAP source (Windows Phone or Silverlight).
Specifies the active configuration. You can add any number of configurations. This makes it possible to create multiple output files with different properties easily.
Specifies the default language. It is used when building if the active build language does not contain any value.
Check Use language fallback if you want to use fallback languages. Fallback language is a parent language. For example, German (de) is the parent language of Swiss German (de-CH).
Specifies the output directory when Soluling creates output files. By default, the default output directory is used. In most cases, this is what you need. However, if you want to use a different output directory, click the Custom radio button and click the ... button to select the output directory.
Specifies what kind of output files are created in the creation process. Possible values are:
Value | Default | Description |
---|---|---|
Localized | Yes | Soluling creates one package file (.xap) for each language. Each package contains either a localized assembly file instead of the original assembly file or an original assembly file and satellite assembly file. How to localize package files specifies which one to use. |
Multilingual | No | Soluling creates one package file that contains original assembly files and several satellite assembly files for each original assembly file. There are as many satellite assembly files for each assembly file as there are output languages in the project. |
Specifies options for the XAP file.
Value | Description |
---|---|
Use a custom manifest file | Check this if you want Soluling to use a custom AppManifest.xaml file when creating localized application files. The custom file must locate in the same directory as where the application file will be created. |
Create run page | Check this if you want Soluling to create an HTML file that runs the localized Silverlight application. The run page will be created on the same directory as the localized application file. This option is visible only when localizing Silverlight applications. |
Specifies how the assembly files in the localized packages files are localized. Possible values are:
Value | Default | Description |
---|---|---|
Replace the original assembly file with the localized assembly file |
Yes | The localized package contains a localized assembly file instead of original assembly file. |
Add satellite assembly file | No | The localized package contains the original assembly file and satellite assembly file. |
This is visible only when Localized files check box is checked in Output files. If only Multilingual file is checked then this is hidden because multilingual XAP files always use satellite assembly files.
Let's have an example. Your original XAP file (Application.xap) contains a manifest file (AppManifest.xaml) and assembly file (Application.dll). You have two target languages in the project: French and German. The following table contains the output files that Soluling creates.
Output file + How to localize package files | Files that are created | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Localized package files |
fr\Application.xap
de\Application.xap
|
||||||||||||
Localized package files + Add satellite assembly file |
fr\Application.xap
de\Application.xap
|
||||||||||||
Multilingual package file | all\Application.xap
all\RunPage.bat An HTML file that runs the multilingual application and lets the user to switch the language. Created when localizing Silverlight applications. |