nRF Connect for VSCode unlimited number of issues

[Burt]

Hi, I have several issues just to start off with. One is when I generate support information, it does its thing, and then stops, and I have no idea where the support information was put. Based on instructions to another customer, that is not supposed to happen. It did not happen for them apparently, but it happened to me.

The next problem is when I start VS Code from the toolchain manager on Linux, v2.0.0, west is not found.

The next problem is when I start VS Code from the command line on Linux, cmake  --version gives an error in VS Code, although it is perfectly fine on the command line.

Basically I can do almost anything in a Linux terminal with regards to building and debugging nRF9160 projects, but on Linux I cannot build or debug, and on Windows I can build but not debug, when VS Code is involved.

I have never ever seen an IDE in many, many years that is quite so indecipherable. This is really crazy. Perhaps you can fix that or switch to another recommended IDE?

Thanks.

Burt

[Michal]

Hello Burt,

Sorry for the late answer, I am going to check it on Windows tomorrow. Thank you for all the feedback.

By the way, a small tip for the future: for inserting code/log snippets I would recommend clicking insert->Code in the text editor. Makes things easier to read and follow.
Like in this screenshot:

Best regards,

Michal

[Burt]

Thanks, Michal, looking forward to your findings and help. By the way, you pointed me earlier to a release note. This is just an aside, but a couple of things in it, in this sentence from that release note:

We have disabled the build system problem-matcher for C code, as it duplicates the IntelliSense errors, but does not update the errors as you edit. 

did not seem to be 100% accurate. The IntelliSense errors--they are really Code Analysis errors, correct? And by default, Code Analysis only runs when you right click and command it to run. It's no problem to change the default--in which case the errors are updated each time you save the file. It would be nice to know if the person who wrote that line was thinking of some type of error that I am not thinking of or is it simply a misstatement. I think that the IntelliSense in Microsoft Visual Studio has more features than that in VS Code--perhaps some error detection.

Thanks, Michal.

Burt

[Burt]

Hi Michal,

Where did you go--I was hoping to hear your results on Windows. I am wondering if you had to order a Windows computer from the manufacturer and then there were supply chain issues! Seriously, I hope you were able to reproduce the problem.

Burt

[Michal]

Sorry, I was checking this out a bit, but weren't sure about a few things and forgot to post a reply.

I think that intellisense has been merged with code analysis, but it feels like for me that they work in a bit different way still? A bit hard to find the exact information around that. But maybe that is because of those errors blocking warnings, as you said.

I did also get the red carat and similar kind of errors when using the code analysis.

I will get into dialogue with the developers again about that issue.

Best regards,

Michal

[Burt]

Thanks, Michal. Both Intellisense and code analysis Clang-tidy exist in the C++ extension, and I don't think they are merged other than in the sense that they both are part of the C++ extension. Visual Studio Code C++ December 2021 Update: clang-tidy - C++ Team Blog (microsoft.com)

I am happy that you were able to reproduce my issue using code analysis and thank you for discussing it with the developers.

Burt