We are having issues getting JS issues to appear inside Visual Studio but not C# or C++. The rules seemed to have been correctly pulled from the server and in the output I can see it recognises issues on various lines, but these aren’t translated to actual issues inside Visual Studio for some reason. This is also the case in standalone mode. I have attached the output in case there is something relevant there. Thanks.
Make sure that when you install NodeJS, that you check the box to add Additional Tools. Without this, I noticed that things do not work the way they’re supposed to. During this installation, there is an extension that gets added to Visual studio
Hi, I have tested the behaviour again including the above solution with Node.
Using the same solution and .js file, I can now get issues to appear in the errors list inside VS but only when used in standalone mode. As soon as I use it in connected mode the issues are still found (based on the logs), but don’t appear inside VS. I have attached the logs from both test cases to see you can spot anything useful.
I have updated the version and can confirm the problem still exists for 8.10. Let me know if it would be helpful to get additional logs for this version too.
Thanks for the response. I have retested on 8.10 and with a real production file so I could compare to the SonarQube server.
Looks like all the issues that appear in standalone inside VS are also present and open inside the SonarQube server. Similarly the issues that appear in the log for connected mode are also present in the SonarQube server (e.g. S1117 on line 119 from the connected log is listed as an open issue in SonarQube).
I still just don’t see the issues inside VS when in connected mode even though they are being found in the logs.