References to Platform-Specific Files

In the code, you need to reference your platform-specific files with their corresponding file group name. File paths need to be relative to the root.

If an existing app contains files that AppBuilder identifies as platform-specific, you might need to change existing references or rename the files. If a third-party framework contains files that AppBuilder identifies as platform-specific, reference them with the name of the file group or rename the files.

AppBuilder nests platform-specific files such as name.ios.extension in a file group named name.extension. During the build process, AppBuilder uses the file group name when adding the platform-specific file to its corresponding application package.

In your code, reference name.platform.extension files as name.extension files. For example, if your file is named main.wp8.css, reference it as main.css in your code. During a build for Windows Phone, AppBuilder will pick up main.wp8.css, rename it to main.css and include it in your app.

AppBuilder nests platform- and configuration-specific files such as name.debug.ios.extension in a file group named name.debug.extension. This file group is nested inside a file group named name.extension. During the build process, AppBuilder uses the top file group name (name.extension) when adding the platform- and configuration-specific file to its corresponding application package.

In your code, reference name.configuration.platform.extension files as name.extension files. For example, if your file is named main.debug.wp8.css, reference it as main.css in your code. During a debug build for Windows Phone, AppBuilder will pick up main.debug.wp8.css, rename it to main.css and include it in your app.