SonarQube extension stopped showing issues in error list

@jaromir Could you please check if your specific issue is similar to this one instead: Issue reporting stopped since version 9.0.0 in VS - #13 by aandre

@georgii.borovinskikh yes, it looks similar → do you know how to fix the issue? or any workaround?

Thanks
Jaromir

Unfortunately, not at the moment:

Please follow the other thread for updates :slightly_smiling_face:

1 Like

Summary of investigation

After the investigation, I’ve found that this is the problem:

Trigger

The default location for cloned repositories in VS is ~\source\repos. When using VS’ clone ui, it is being set to ~\Source\Repos\<git repo>.

Bugs (to be fixed)

  1. when we search for Documents to analyze inside the Roslyn Solution, we use case-sensitive search
  2. when we map diagnostics to sonar issues, we use case-sensitive file path mapping

Workaround

The workaround is to use File > Open > Project/Solution menu in VisualStudio to open the same solution using the correct (lower case) path.

1 Like

I can confirm that the workaround of using File > Open > Project/Solution works for me.

1 Like