Known Issues

List of known problems (last update 2015-03-30):

1. Warning about the Linker's OutputFile property value is shown on each Build. It doesn't harm the build process.

Workaround: Visual Studio doesn't allow empty extensions for produced binaries. Set any extension (like: .exe, .bin, .so) and update the bar-descriptor.xml accordingly and the warning should disappear.

2. Project doesn't compile, when path or binary contains a space.

Comment: This is the limitation of underlying make system. Visual Studio nor GDB doesn't have this problem, so some other functionalities may work. Suggested approach is not to use spaces in names at all.

3. Deployment of an application, could block Visual Studio.

Comment: Please wait until the deployment completes.

4. The bar-descriptor editor removes all comments (#27)

Comment: No workaround for now.

5. Opening any BlackBerry project disables IntelliSense error highlighting.

Comment: Since the NDK headers are designed for qcc (gcc), they mostly don't define the correct types suitable for VisualC++ compiler nor IntelliSense. That's why the plugin disables error highlighting, when BlackBerry project is opened and restores it, when the solution is closed. Otherwise almost whole source-code in an application could be red underscored. However, the IntelliSense is smart enough to ignore those missing types and provide full contextual help, while developing C/C++ applications.

6. Sometimes after breakpoint hit in Cascades application Frame not in module window is shown instead the source-code.

Workaround: Open 'Threads' window or press the refresh button next to any variable in 'Watch' window.

7. Logs seem to be cut or disturbed.

Comment: This is the known issue with captured console logs, when you write cards application. From the BB10 OS perspective, when you invoke the card, it starts the same application process again (or more if more cards are invoked) and all those processes write to the same log file. It's not the fault of the plugin though.

8. Console logs and slog2 messages doesn't reflect the code flow.

Comment: Some single console and slog2 logs might appear in reversed order, other than expected as it seems to be written in source-code (example: write console log before and after call to bsp_initialize()) since they are received via two separate data-streams from the device. Unfortunately BB10 OS doesn't provide any way to sync them, so they are just printed, when delivered.

Workaround: Please keep the one way of producing logs or knowing the root cause of this issue - just ignore it. Decreasing the console-logs refresh time can sometimes help a bit.

9. Auto-update-MSBuild feature of the package from inside Visual Studio 2010 fails on Windows XP.

Comment: Default settings of the RunAs dialog prevent from manipulations inside "Program Files" folder. To upgrade without any issues uncheck the "Protect my computer and data from unauthorized program activity" next to the current user name.