July 28, 2015
This section contains the major new features and improvements that AppBuilder 2.11 introduces.
This release of AppBuilder introduces the following features and improvements in the AppBuilder in-browser client.
This release of AppBuilder introduces the following features and improvements in the AppBuilder extension for Visual Studio.
This release of AppBuilder introduces the following features and improvements in the AppBuilder command-line interface and AppBuilder package for Sublime Text.
appbuilder help plugin add
appbuilder help plugin configure
appbuilder appmanager upload
appbuilder cloud export
This release of AppBuilder introduces the following features and improvements in the NativeScript companion apps.
This section contains the major bug fixes that AppBuilder 2.11 introduces.
Access to this method requires an authenticated user
Error: Invalid url: ''. Url must start with prefix: 'nativescript:'.
This section contains the major breaking changes that AppBuilder 2.11 introduces.
Renamed the appbuilder feature-usage-tracking command to appbuilder usage-reporting in the AppBuilder command-line interface. You need to update existing scripts which call appbuilder feature-usage-tracking to call appbuilder usage-reporting instead.
If your project targets Apache Cordova 4.0.0 or later, the Telerik Analytics, Telerik Mobile Testing and Telerik AppFeedback plugins are available as verified plugins from the Telerik Verified Plugins Marketplace and not as integrated plugins from the Project Properties dialog.
When you update your project to target NativeScript 1.1.2, you might experience multiple issues due to breaking changes in the APIs. For more information about the major changes in NativeScript 1.1.2, see Changelog for the cross-platform modules, Changelog for the iOS runtime and Changelog for the Android runtime.
For more information about how to migrate your project to NativeScript 1.1.2, see Configure the Target NativeScript Version.
Migrating between NativeScript versions completely replaces the tns_modules folder. Any custom modules or files will be lost. To be able to use any custom modules, make sure that they are available as npm packages and list them in the dependencies section in the package.json file in the root of the project. The AppBuilder will resolve them on build. For more information about the dependencies syntax, see Specifics of npm's package.json handling.
Post your feedback in the Platform UserVoice portal or the public forums
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.