Please provide
- Operating system: Win 10 Pro.
- Visual Studio version: Microsoft Visual Studio Community 2022 (2) (64-bit) - Current
Version 17.13.4 - SonarQube for Visual Studio plugin version: SonarQube for VS V8.16
- Programming language you’re coding in: C#
- Is connected mode used:
- SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?):
Use Sonar Qube Community Build v24.12.0.100206
- SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?):
And a thorough description of the problem / question:
I have a Sonar Qube Community analyzing remote repo but I want to have a local code analyze before I submit to cloud. So I add the SonarQube for VS extension. Then I create a Project token from SQ community and bind the project using this token.
And then I restart my VS and the analyze worked but not as expected. The code analyzing result have more validation errors then I summit it to remote.
Why do local plugin have different analyze report from server after I already bind it to server? And how can I do to make the local plugin use same analyze rule with server.