With build configurations, you can customize your apps to create application packages for debugging or distribution. In Progress AppBuilder, you can customize and apply the Debug and Release build configurations, aimed at testing and production, respectively.

Applying Build Configurations

When you set a build configuration for your application package, AppBuilder automatically applies the following changes to your app.

Option Description
Debug
  • Includes any *.debug.* files in your application package, removes the debug modifiers from the file names and renames them to *.*.
  • If applicable to the AppBuilder client, applies any additional exclude or include rules defined in .debug.abignore.
Release
  • Includes any *.release.* files in your application package, removes the release modifiers from the file names and renames them to *.*.
  • If applicable to the AppBuilder client, applies any additional exclude or include rules defined in .debug.abignore.

Build Configuration Specifics and Limitations

When you work with build configurations in AppBuilder, keep in mind the following specifics and limitations.

Specifics

  • When you load your app in the NativeScript developer app via QR code, AppBuilder applies the currently set build configuration.
  • When you load your app in the NativeScript developer app over cable, AppBuilder always applies the Debug configuration.
  • When you load your app in the NativeScript developer app from your account from the Platform companion app, AppBuilder applies the build configuration currently set in the Platform companion app.
  • When you run your app on device as an application package, AppBuilder applies the currently set build configuration.
  • When you run your app in the native emulators, AppBuilder applies the currently set build configuration.
  • When you work with configuration-specific files (*.debug.* and *.release.*), AppBuilder takes the file that matches the currently set build configuration, renames it to *.* and includes it in your application package.
    For example, when you run a build with the Debug configuration, AppBuilder takes index.debug.html and includes it in your application package as index.html.
  • When you work with configuration-specific files (*.debug.* and *.release.*), in your code, reference these files without the configuration modifier (debug or release).
    For example, the correct reference to index.debug.html is index.html.

Limitations

  • Do not create and work with platform- or configuration-specific package.json files. AppBuilder might not be able to process them correctly in the in-browser client, classic Windows desktop client or the extension for Visual Studio and you might experience various issues when working with your app.
  • To work with files which are platform- and configuration-specific simultaneously (*.debug.ios.* or *.release.android.*), your file names must use the following format:

    name.configuration.platform.extension
    
    index.debug.ios.html
    index.debug.android.html
    index.release.ios.html
    index.release.android.html
    

In this section, you will find the following resources:

Start a free trial Request a demo
Contact us: +1-888-365-2779
sales@telerik.com
Copyright © 2016-2017, Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.