I’m trying to run code analysis on project files, but the .vb files in the project are not being scanned even though we are using Quality profile with VB rules. Can you please help on this issue.
SonarQube server version: Enterprise Edition - Version 8.9
We have installed SQ on a server(Enterprise Edition - V 8.9) and trying to analyze a project which includes VB.NET files. Please find below screen shot on what we were seeing in SonarQube .vb file analysis. Except .vb files all other extension files we can see analysis data like loc,bugs etc.
There’re VB6 and VB.NET available on SQ Enterprise Edition and they share *.vb file extension. You should be able to confirm this theory in verbose logs.
You can try adding this parameter /d:sonar.lang.patterns.vb="*.bas" to reset VB6 file extensions for your VB.NET analysis. If it helps, you can reconfigure registered extensions in your project settings/languages on your SQ instance.
If this theory doesn’t help, please check logs in verbose mode for more clues.
We have updated language patterns as mentioned above but didn’t find anything and same issue persists as above image. At first after updating it failed with conflict since it has .vb and .bas in both vb.net and vb6. later on tried patterns only for vb.net and it didn’t work.
Hi,
How did you setup your analysis? The logs indicate that you’ve used Azure DevOps extension. Is that correct?
What are the parameters that you’ve passed to the extension?
It seems that you’ve explicitly configured sonar.modules that doesn’t match your module GUIDs, resulting in overriding the autogenerated stuff. Can you remove the explicit sonar.modules?