Release notes for BlackBerry Native Plug-in for Microsoft Visual Studio (version 2.0 Gold)

Related release notes

MD5 checksum file

An MD5 checksum file is available for releases of the BlackBerry Native Plug-in for Microsoft Visual Studio. You can use this file, in conjunction with any checksum tool that supports MD5, to validate the installer files that you download. Use the following link to download the MD5 checksum file:

Visual Studio plug-in checksum

Known issues


In VS2013, when a conditional breakpoint is set before starting a debug session and the breakpoint is hit, the debug session times out.


When you are debugging a project on the simulator or a device, if you hit a breakpoint and then turn off the simulator or device, the project debug session is not stopped. If you try to continue debugging, Visual Studio waits for a response from the simulator or device.
Work Around: To stop debugging, you need to click Stop.


When you are debugging on a BlackBerry simulator or a device and you are stopped at a breakpoint, if you close the application, the corresponding debug session running in Visual Studio does not end. Debugging continues as if the application is still running on the simulator or device when you click the Step In, Step Out, Step Over buttons.
Work Around: You can stop the debug session within Visual Studio by clicking the Stop or Play button which causes Visual Studio to recognize that the application is closed.


The Qualifier drop-down menu does not show the device IP settings.
Work Around: After entering the BlackBerry settings data, start debugging an app. After debugging, the plug-in starts updating the Qualifier from the Attach to Process window, and then you can modify the Device/Simulator IP and that change will be reflected immediately. This issue is reproducible in 32 and 64 bits environment, for both VS 2012 and 2013.


Projects with spaces in their pathname will fail to debug.
Work Around: Avoid putting projects in folders with names that contain spaces.


The following features of Microsoft Visual Studio are currently unsupported in the BlackBerry Native Plug-in:

  • Modifying Local Variables from the Locals Debug Window
  • Breakpoint Filters


A warning relating to the Linker's OutputFile property value appears on Build. This warning does not affect the build or deployment process.


While debugging, if you hit a breakpoint and attempt to edit a local value from the Locals Window, the value is not updated immediately. You can see the correct value using the Watch and Immediate window, or you can pass the mouse over the variable. After stepping into/over, or after hitting another breakpoint, the value is refreshed automatically.


If you continue execution after hitting breakpoints, debugging works as expected and stops at each subsequent breakpoint. If you continue execution after stepping through breakpoints, some subsequent breakpoints will be skipped. (201809)


If you deploy an application in non-development/signed (Release) mode and then redeploy it in development/unsigned (Debug) mode, the subsequent deployment fails, as blackberry-deploy attempts to overwrite a signed application, which is read only.
Workaround: Manually delete the signed application from the device and then redeploy it.


Once you start a deploy, you must wait until the deploy completes.


When you create a Simulator-Debug folder, a Device-Debug is created as well. The Device-Debug folder does not cause any issues and can be deleted.


If you are debugging and your device screen locks, debugging stops until you unlock your screen.
Workaround: Set the device screen lock time to a longer time.


The bar-descriptor.xml file editor strips out all comments when you open the bar-descriptor.xml file
Workaround: Save the file.


Changes made to the bar-descriptor.xml file are not reflected on the device.
Workaround: Manually remove the application from the device and deploy the application again.


While deploying, you may get the error message, 'Error 1 error MSB6006: "blackberry-nativepackager.bat" exited with code 1'.
Workaround: Delete the project and relaunch.


If the platform configuration is set to Release while still in debug mode, debug mode continues.
Workaround: Click Stop and the IDE will exit from debug mode. The application on the device will exit.

Last Modified: January 24, 2014

  1. 1. Download the tools

    Before you start developing, you'll need to visit the Downloads tab. Here you'll find downloads for the BlackBerry 10 Native SDK, BlackBerry 10 Device Simulator, and some other useful tools.

  2. 2. Try the sample apps

    Now featuring a filter control, the Sample apps tab allows you to search for samples by name or by feature.

    Select either the Core or Cascades radio buttons to display the samples relevant to you.

  3. 3. Educate yourself

    The Documentation tab contains tons of examples, tutorials, and best practices to guide you along the path towards building an awesome app.

    You can access all the documentation that you need in the left-hand navigation.

  4. 4. Start developing

    The Reference tab is where you'll find essential details about how to use our APIs.

    You can use the left-hand navigation to choose how you would like to browse the reference: by module, by topic, or alphabetically. If you have an idea of what you are looking for, start typing it in the Filter box.