MicrosoftGame.config can be localized to the user’s locale. Visual Studio 2019+ auto-generates a resources.pri file that the OS looks up at runtime.
Dump the file from the GDK command prompt:
Localizing app name and description
Add default strings
- Right-click your project in Solution Explorer and add a New Filter named
Strings. - Right-click
Stringsand add a New Item > Assembly Resource File (.resx). VS createsresources.resxat the package root.
The GDK requires
.resw. Rename resources.resx to resources.resw.Reference strings in MicrosoftGame.config
Add per-language strings
Create aStrings/<lang> filter per supported language, add an Assembly Resource File under each, set Item Type = PRI Resource, and rename to .resw.
Declare languages in MicrosoftGame.config
zh-SG and zh-CN for fallback.
Localizing images
Logo, SmallLogo, SplashScreen, StoreLogo can be localized:
- Add per-language subfolders under a shared folder (e.g.
Images). - Add images with Item Type = Image, Content = Yes.
- Provide default images at the root as fallbacks.
Include at least one image resource. Otherwise localized strings won’t resolve and the title’s name shows as
ms-resource:AppName.Chunk layout
Intelligent Delivery
Tag chunks withLanguages:
Install behavior
- Console
en-US→ installs 1005 and 1008. - Console
en-GB→ falls back toen-US→ installs 1005 and 1008. - Untagged chunks always install.
Testing with xbapp
/Languages— install for listed languages regardless of console setting./AllChunks— install the entire package./w— keep the connection open after install.
See also
Related API documentation
- XPackage API reference — mount/enumerate localized package chunks
- MicrosoftGame.config elements reference — resource + chunk declarations
