HTML and CSS Reference
In-Depth Information
Localizing an application name
There are some situations in which the application has a name that is “neutral” to spoken languages.
In such cases, you won't ever want to change the name regardless of how many languages you
localize the application for. This is, however, a very special situation. More likely, you might want to
translate—or just change—the name of an application based on the language used by its intended
audience. Using a different name for each supported language is a recommended (not mandatory)
approach. If you plan to use localized names, the page in Figure 14-9 shows how to proceed.
FIGURE 14-9 Choosing localized names.
After reserving the name, you can start packaging the application.
Note As mentioned, if the name is truly important for the application, then you should first
reserve the name and then start developing the application.
packaging an application
The packaging step consists of creating a single container with all the files that make up your
application. Before you start packaging, you should ensure that the application is feature-complete
and contains no bugs or vulnerabilities.
Compiling in release mode store logo.png
A finished Windows Store application is an application that needs no further changes to the code and
has defined files for the various logos and the splash screen. In addition, you might also want to have
some screenshots ready that help advertise the application in the Windows Store. Pay attention to the
file: that will be your application's icon in the Windows Store.
When everything is ready, you first compile the application code in Release mode. When you
compile an application, you usually choose between two modes: Debug (the default) and Release .
Both modes produce a valid executable file; however, the Debug mode pads the executable
Search WWH ::

Custom Search