Visual Studio Code nRF Connect SDK improvements

Hello !

I'm currently discovering the VS code extension for nRF Connect SDK and I whish to give some feedbacks of missing / odd features. I hope this is the best place !

I am used to work with Segger Embedded Studio when developing with nordic. So this is basically a "missing features overview" regarding SES.

1) With VS Code, there is no "Code Outline". In fact there is something similar with VS Code "Ctrl + Shift + O" but this is really less clear.

2) When bulding / Flashing, it is never clear if you "rebuild all" or just "build". Same for flashing : you do not have the choice to rebuild or not direclty.

3) When using "Debug" feature (step by step). Every time I lauch a new session, I receive an error message that gdb has failed... But in fact it succeeds ^^

4) Error and warning are strangely erased : I am never sure if messages come from last build or current build

5) Naviguating in files is a mess : when I use "Ctrl + click" on a function or variable, I drop in the correct file but sometimes not to the correct line at all ! Moreover with SES you can "find in files" even for files of the nRF Connect SDK. This does not seem to work the same way with Visual Studio Code.

6) Creating a new project from sample with west workspaces does not work for me : it always fail on one of the repository. And after this point, the VS Code extension just give up.

7) I do not understand why nordic is pushing the community so hard on VS Code while it is obivously less clear and misses features that are already here with SES (even if it is not perfect).

I guess some of these points are a misunderstanding of VS Code or the extension but I hope these are useful feedbacks ! Smiley

Best regards !

Parents
  • I second #7 there.  SES is way more predictable and it's a good platform that runs well. 

    I was playing with VS code just a bit this morning on my Mac and wanted to get back into it again to learn some more about the problems I'm going to run into when I need to switch to it.  Much to my surprise, when I opened it up, it had updated itself.

    Now, in this particular case, updating itself is what I was going to do but that's a BAD thing to do without asking me about it. Way, way bad.  If I was in the middle of a dev cycle, that would have blown my schedules all up because now I have a tool that I know nothing about.  Bad. Very Bad behaviour.

    SES at least tells you about the thing needing some updates so you can ignore it.

  • Hi, 

    Appreciate your feedback.

    NCS only supports VS Code since v2.0.0. Before that version, you still can use SES.

    If you have any other issues, please create a new support case. 

    Regards,
    Amanda H. 

Reply Children
No Data
Related