Release notes for BlackBerry Native Plug-in for Microsoft Visual Studio (version 2.0 beta)
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:
This section lists known issues for the BlackBerry Native Plug-in (version 2.0 beta) for Microsoft Visual Studio.538
If you are using the 10.2.1 runtime, you need to use the 10.2.0 API level to deploy to a device or a simulator.
- Make sure you have downloaded and installed the 10.2 API level of the BlackBerry 10 Native SDK.
- In C:\qconfig, make a copy of qnx_blackberry_native_development_kit_10.2.0.1155.xml.
- Rename it with the OS version that is being used in your device or simulator. For example, qnx_blackberry_native_development_kit_10.2.1.1055.xml. You can find the version on your device by navigating to Settings > About > OS Version.
- Open the new file with an XML editor.
- Update the <version> and <detailedVersion> fields with the correct API level version. For example, 10.2.1.1055.
- Update the <name> field with a name that will remind you that you have created this workaround. For example, BlackBerry Native SDK 10.2.1_mine.
- Save and close.
- In Microsoft Visual Studio, on the BlackBerry > Settings menu, select the correct API level. For example, BlackBerry Native SDK 10.2.1_mine.
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
Using the PlayBook API level 2.1, debugging does not start if the app is already installed.
Workaround: Delete the app on the PlayBook before starting to debug.
A warning relating to the Linker's OutputFile property value appears on Build. This warning does not affect the build or deployment process.485
When you attempt to deploy your application the output "Deploy: 0 succeeded, 0 failed, 1 skipped" might appear. Ensure that the Deploy checkbox is selected in the Configuration Manager.484
Debug breakpoints aren't hit on the BlackBerry PlayBook.
Workaround: Since short path names are used by GDB (e.g., /src/PARTIC~1.CPP), ensure source files are named differently to avoid conflicts.
The application will deploy to the device but the debugger will not be attached.
Work Around: Start debugging using the play button in the tool bar. (201809)
If you have a device or simulator which is not set up correctly, and you attempt to debug or deploy your project, the project builds and attempts to deploy, but fails. You will be unable to interact with Visual Studio while it is building and attempting to deploy. At the end of the process, you are informed of the unsuccessful build/deploy and you can then continue.460
If you have the plug-in installed and you uninstall all the API levels, and then you try to attach a process, an error occurs and Visual Studio crashes.
Workaround: Uninstall the plug-in.
Before starting the BlackBerry Native Plug-in for Microsoft Visual Studio you must have a stable internet connection to avoid unexpected or unstable behaviour.441
While debugging, the When Hit feature may not work as expected. For example, variables may not be printed or evaluated and the program may break even if Continue Execution is selected.254
If you try to attach to a running process on a device with code that is different than the compiled code on the device, you could be presented with segmentation faults in some environments.252
You can't attach a process using PlayBook API level 2.1.172
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)170
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.141
Debugging a multi-threaded application on a PlayBook can hang debugging.
Workaround: Stop the debugging, remove the breakpoints in the thread, and begin debugging again.
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.
Setting MSBuild project build output verbosity to Quiet requires you to build twice.
Workaround: Set the build output to Minimal/Normal/Detailed.
Opening a bar-descriptor.xml file using File > Open (or CRTL-O) while the project tree is not open in the solution causes errors.129
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.
Cancelling the Break Function window causes an error message.
Workaround: Put back the missing breakpoint.
On Windows 8, unable to run a macro when a breakpoint is hit.125
Able to build a project while in a debug session.
Workaround: Stop the debug session, build the project, and start a new debug session.
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: December 5, 2013